No Maven Central release about spoon

[pschichtel]

I could make a Pull Request with the setup we use for our projects.

[pschichtel]

That would look similar to this: https://github.com/CubeEngine/MessageCompositor/blob/master/pom.xml

[monperrus]

Hi Phillip,

Thanks for the issue. Going back to Maven Central is indeed in the roadmap of the project.

How is authorization handled to publish a new version on Maven Central?

--Martin

[pschichtel]

They use their JIRA for registration and once you got approved you just put a section in your local maven configuration with your JIRA login information and the ID of your configured central repository in .

More information about the process:

• Sonatype OSSRH Guide
• Central Sync Requirements
• Guide to uploading artifacts to the Central Repository

[pschichtel]

http://gforge.inria.fr/frs/shownotes.php?release_id=8745

• pom.xml not updated
• still no central release

Why did I even make the pull request to fix everything up for a release?

[monperrus]

Hi Phillip,
Thanks again for the pull request which is now merged. Uploading to
Central is on our todo list.
What else do you mean?

[pschichtel]

A new status on this?

[GerardPaligot]

Hello Phillip,

Yes, I push on Maven Central today. :)

[seintur]

Hi @GerardPaligot

Thanks for the deployment in Maven Central.

It seems that the jar http://search.maven.org/remotecontent?filepath=fr/inria/gforge/spoon/spoon-core/2.3/spoon-core-2.3.jar contains a log4j.properties file with the following line 10:

log4j.appender.R.File=/var/folders/yd/kdk6_3wn4fvc71sblyjpgnn80000gn/T//spoon-log.log

I'm a bit confused since the original file as stored in the git repo https://github.com/INRIA/spoon/blob/master/src/main/resources/log4j.properties contains instead:

log4j.appender.R.File=${java.io.tmpdir}/spoon-log.log

Practically, when running Spoon 2.3 fetched from Maven central, I bump into the following exception:

log4j:ERROR setFile(null,true) call failed.
java.io.FileNotFoundException: /var/folders/yd/kdk6_3wn4fvc71sblyjpgnn80000gn/T/spoon-log.log (No such file or directory)

which is obviously evident given the log4j.properties.

Wat do you think?

Lionel.

[pschichtel]

Well someone forgot to disable resource filtering...

maven will replace ${...} macros and the velocity context to do this contains all java properties.

[GerardPaligot]

Hi,

I discussed the problem with @monperrus and we modified the log4j.properties in the commit. c7af8e2.

I'm repushing on maven now. You will see it at the end of this morning or in the afternoon.

[pschichtel]

You might want to check the commit comments first

[GerardPaligot]

Yes, I saw them after my message.

[GerardPaligot]

Well, I made a PR #55 to improve pom.xml to disable filtering on the log4j.properties file. If it is ok for all, we merge it and I re-push on Maven Central.

[GerardPaligot]

I'm re-pushing on Maven Central now. It should appear on the website in some hours.

[pschichtel]

Why didn't you use the release plugin??

[GerardPaligot]

I used maven release plugin.

[pschichtel]

Well the release commits in git are missing as well as the tag. This leads to the problem the a) the source code used to build the release in maven central is not actually available and b) the pom.xml in this repo has the wrong version as it should be 2.3.2-SNAPSHOT or 2.4.0-SNAPSHOT

[GerardPaligot]

Ah yes, this is "normal". We don't release on this Git project but on another one. @monperrus must to push commits and tag of the release plugin from the another git projet to this GitHub project (because, I can't myself, I don't have these privileges).

[monperrus]

Tag is now on Github.

[pschichtel]

Just an idea: It might be good to automate the mirroring from the internel repository to github. I once did that with a small post-receive-hook and a deploy key.

Anyway: This issue is now finally closed, I hope this will continue in the future.