-
-
Notifications
You must be signed in to change notification settings - Fork 107
Parent pom upgrade #17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
The plugin suports Java 7 only, hence such upgrade is really reasonable
|
Needs a FindBugs cleanup |
|
@oleg-nenashev we are using this plugin on Jenkins instance running Java 8 -- what do you mean by "de-facto the plugin supports Java 7 only"? |
|
@jakub-bochenski Sorry for missing the ping. I meant that Java 6 is not supported, sorry for confusion as well |
|
@oleg-nenashev no problem. I've edited the original message to reflect this. On the topic of this MR: I don't feel that I understand all the consequences of doing this change. |
7291f87 to
3488ecc
Compare
@oleg-nenashev ping? |
|
@jakub-bochenski sorry, missed the pings. |
|
in #40 upgrading to 3.2 |
…om-upgrade # Conflicts: # pom.xml # src/main/java/jenkins/plugins/logstash/LogstashBuildWrapper.java
b80e651 to
617cc72
Compare
pom.xml
Outdated
| <parent> | ||
| <groupId>org.jenkins-ci.plugins</groupId> | ||
| <artifactId>plugin</artifactId> | ||
| <version>2.15</version> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Now it's a downgrade, since pom is at 2.15
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Right, I messed up the merge
pom.xml
Outdated
| </parent> | ||
|
|
||
| <properties> | ||
| <jenkins.version>1.625.3</jenkins.version> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should bump back to 2.7.4
| @SuppressWarnings("deprecation") | ||
| @Initializer(after = InitMilestone.JOB_LOADED) | ||
| public void migrateData() | ||
| public static void migrateData() |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
actually what is the reason for making this method static?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The initializers are always static. The code won't even compile in newer versions otherwise IIRC
|
Is there any update on this? |
|
Hi @oleg-nenashev and @jakub-bochenski, most parts of this pull request are superseded by pull request #81. |
|
@darxriggs I think what is left is only the initializer conversion to static; any reason you left it out of #81? |
|
I found this pull request afterwards. Mine was really just about pom.xml and cleaned up much more in it. |
#17 - [x] Pick latest parent POM with build flow fixes