Skip to content

Conversation

@oleg-nenashev
Copy link
Member

@oleg-nenashev oleg-nenashev commented Sep 16, 2016

#17 - [x] Pick latest parent POM with build flow fixes

  • Core dependency is upgraded to 1.625.3, because de-facto the plugin supports Java 7+ only. Hence it's better to go forward
  • Restored injected tests, which have been disabled in the plugin

@oleg-nenashev
Copy link
Member Author

Needs a FindBugs cleanup

@jakub-bochenski
Copy link

@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"?

@oleg-nenashev
Copy link
Member Author

@jakub-bochenski Sorry for missing the ping. I meant that Java 6 is not supported, sorry for confusion as well

@jakub-bochenski
Copy link

jakub-bochenski commented Nov 15, 2017

@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.
Please merge it if you think it's safe (I assume you have the perms if not let me know)

@jakub-bochenski jakub-bochenski force-pushed the parent-pom-upgrade branch 3 times, most recently from 7291f87 to 3488ecc Compare November 27, 2017 16:02
@jakub-bochenski
Copy link

Please merge it if you think it's safe (I assume you have the perms if not let me know)

@oleg-nenashev ping?

@oleg-nenashev
Copy link
Member Author

@jakub-bochenski sorry, missed the pings.
Ideally it needs another update to Parent POM 2.37 or above, but it can be done later since it may require more work

@akostadinov
Copy link

in #40 upgrading to 3.2
There are a number of FindBugs warnings that I just suppressed, can be fixed in future PRs.

…om-upgrade

# Conflicts:
#	pom.xml
#	src/main/java/jenkins/plugins/logstash/LogstashBuildWrapper.java
pom.xml Outdated
<parent>
<groupId>org.jenkins-ci.plugins</groupId>
<artifactId>plugin</artifactId>
<version>2.15</version>

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

Copy link
Member Author

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>
Copy link
Member Author

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()

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?

Copy link
Member Author

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

@darxriggs
Copy link

Is there any update on this?

@darxriggs
Copy link

darxriggs commented Nov 7, 2018

Hi @oleg-nenashev and @jakub-bochenski, most parts of this pull request are superseded by pull request #81.

@jakub-bochenski
Copy link

@darxriggs I think what is left is only the initializer conversion to static; any reason you left it out of #81?

@darxriggs
Copy link

I found this pull request afterwards. Mine was really just about pom.xml and cleaned up much more in it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants