Re: My promotion on Apache JIRA
done. On 20 December 2013 21:22, Michael-O <1983-01...@gmx.net> wrote: > Hi PMCs, > > please reply to my promotion in > https://issues.apache.org/jira/browse/INFRA-7120. I'd like to manage release > just like on Codehaus JIRA. > > I need to release Maven Skins Parent 8. > > Thanks, > > Michael > > - > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > -- Olivier Lamy Ecetera: http://ecetera.com.au http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
[ANN] Apache Maven Shared Jarsigner 1.2 Released
The Maven team is pleased to announce the release of the Apache Maven Jarsigner, version 1.2 This component provides some utilities to sign/verify jars/files in your Mojos. http://maven.apache.org/shared/maven-jarsigner/ To use the Maven Jarsigner, add the following dependency to your project: org.apache.maven.shared maven-jarsigner 1.2 Release Notes - Maven Shared Components - Version maven-jarsigner-1.2 ** Improvement * [MSHARED-306] - keystore and alias parameters can be used for both sign and verify jarsigner tool ** Task * [MSHARED-301] - use plexus java 5 annotations instead of plexus javadoc tags * [MSHARED-302] - Use java 5 codestyle * [MSHARED-303] - Jar Signer does not support protected authentication path * [MSHARED-305] - Use maven-shared-utils javatool API Enjoy, -The Maven team tony. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Altering Artifact Versions within Reactor
Hey guys, I was hoping that someone might be able to help me out with an issue I'm having on a plugin I've written. The high level of what the plugin does is automatically change the version number of a project to match whatever the name of the git branch name is that it is on without any physical change to the pom.xml or anything (i'll skip the reason for this as it is not relevant to the question). What I've written so far works great as long as I "install" or "deploy" the artifacts as well. However, it does not seem to work so well from within a "reactor" setup. So here is the reactor scenario Parent \__ ChildA \__ ChildB (depends on ChildA) Well the plugin will properly change the version number of Parent, ChildA, and ChildB and it will properly update the version number of ChildA (that is the dependency list of ChildB) to the branch-SNAPSHOT name. However, well it goes to "resolve" that dependency it does not appear to find it within the reactor artifacts that are created and thus tries to find it from the local or remote repositories instead. Because the install/deploy actually physically modify the pom that is to be "deployed" out, everything works great once you have actually installed/deployed it once. For some reason once it locates the pom file it decides to use the version of the artifact that was built from within the reactor (or so it appears but I haven't tested this part too deeply). What I'm not able to do is get that "initial" build to work correctly though and I do not wish to be forced into doing a "install" or "deploy" to make this work. So the issue appears to be that the DefaultArtifactResolver is unable to resolve it and so what I'd like to know is if there is any way for me to manually put something into the cache or repository or something from an in-memory state that is only for the life of that reactor so that it will resolve correctly to the artifact that was just built from within the reactor and not from a local/remote repository? The code if anyone is interested is up on github at https://github.com/sepatel/maven-scm-version-plugin if it helps people to understand what I'm talking about. Thanks for any help or ideas that can be offered, -- *Justice is nothing more than that which is in the greatest self-interest of the largest portion of the population.*
[ANN] Apache Maven Shared Utils 0.5 released
The Apache Maven team is pleased to announce the release of the
maven-shared-utils, version 0.5
This project aims to be a functional replacement for
{{{http://plexus.codehaus.org/plexus-utils}plexus-utils}} in Maven.
It is not a 100% API compatible replacement though but a replacement
:
lots of methods got cleaned up, generics got added and we dropped a
lot of unused code. Although all
the classes are in different packages from plexus-utils, if the method
is present it will have the same
semantics, facilitating easy conversion.
http://maven.apache.org/shared/maven-shared-utils/
The version 0.5 brings in a new API to execute java tools of the jdk
(jarsinger, keytool, ...).
Release Notes - Maven Shared Components - Version maven-shared-utils-0.5
** New Feature
* [MSHARED-304] - Create a API for java tool
Enjoy,
-The Apache Maven team
tony.
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
[RESULT] [VOTE] Maven Shared Utils 0.5 and Maven JarSigner 1.2
Hi, The vote has passed with the following result: +1 (binding): Olivier Lamy, Hervé Boutemy, Robert Scholte +1 (non-binding): Tony Chemit I will promote the artifacts to the central repo. tony. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Maven Shared Utils 0.5 and Maven JarSigner 1.2 (take 2)
+1 - project can be built from the source-release zip. - rat license check is clean. The site is not correct though, the dependencies-page[1] is empty, but that can be fixed apart from this release. Robert ps. would be nice if the MSHARED-304 had a reference to the revision with the fix. [1] http://maven.apache.org/shared-archives/maven-shared-utils-LATEST/dependencies.html Op Wed, 18 Dec 2013 02:00:18 +0100 schreef Tony Chemit : Hi, maven-jarsigner site is now ok :) Maven shared Utils 0.5 -- The version 0.5 offers a new simple API to execute java tool via commandline builder. This API offers also toolchain support (which makes sense while executing java tools from jdk). This api is now used in maven jarsigner shared component and keytool-api (from keytool-maven-plugin @codehaus). We solved 1 issues: https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11761&version=19180 There are still a couple of issues left in JIRA: http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=11761&status=1&component=15606 Staging repo: https://repository.apache.org/content/repositories/maven-064/ https://repository.apache.org/content/repositories/maven-064/org/apache/maven/shared/maven-shared-utils/0.5/maven-shared-utils-0.5-source-release.zip Source release checksum(s): maven-shared-utils-0.5-source-release.zip sha1: 00aec332db87f6549a31395eded80159efc88de3 Staging site: http://maven.apache.org/shared-archives/maven-shared-utils-LATEST/ Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 my +1 Maven shared JarSigner 1.2 -- The version 1.2 uses the new maven-shared-utils JavaTool API, java 5 and plexus java 5 annotations, and much much more... We solved 5 issues: https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11761&version=19721 There is no more issues in JIRA left :) Staging repo: https://repository.apache.org/content/repositories/maven-064/ https://repository.apache.org/content/repositories/maven-064/org/apache/maven/shared/maven-jarsigner/1.2/maven-jarsigner-1.2-source-release.zip Source release checksum(s): maven-jarsigner-1.2-source-release.zip sha1: 573fa9d50cc08bd65a2bf0d077e6c1b08d70046b Staging site: http://maven.apache.org/shared-archives/maven-jarsigner-LATEST/ Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 my +1 tony. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Maven Shared Utils 0.5 and Maven JarSigner 1.2 (take 2)
On Wed, 18 Dec 2013 02:00:18 +0100 Tony Chemit wrote: Hi, Need one more +1 from a binding voter. Thanks, tony. > Hi, > > maven-jarsigner site is now ok :) > > Maven shared Utils 0.5 > -- > > The version 0.5 offers a new simple API to execute java tool via commandline > builder. > > This API offers also toolchain support (which makes sense while executing > java tools from jdk). > > This api is now used in maven jarsigner shared component and keytool-api > (from keytool-maven-plugin @codehaus). > > We solved 1 issues: > https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11761&version=19180 > > There are still a couple of issues left in JIRA: > http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=11761&status=1&component=15606 > > Staging repo: > https://repository.apache.org/content/repositories/maven-064/ > https://repository.apache.org/content/repositories/maven-064/org/apache/maven/shared/maven-shared-utils/0.5/maven-shared-utils-0.5-source-release.zip > > Source release checksum(s): > maven-shared-utils-0.5-source-release.zip sha1: > 00aec332db87f6549a31395eded80159efc88de3 > > Staging site: > http://maven.apache.org/shared-archives/maven-shared-utils-LATEST/ > > Guide to testing staged releases: > http://maven.apache.org/guides/development/guide-testing-releases.html > > Vote open for 72 hours. > > [ ] +1 > [ ] +0 > [ ] -1 > > my +1 > > > Maven shared JarSigner 1.2 > -- > > The version 1.2 uses the new maven-shared-utils JavaTool API, java 5 and > plexus java 5 annotations, and much much more... > > We solved 5 issues: > https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11761&version=19721 > > There is no more issues in JIRA left :) > > Staging repo: > https://repository.apache.org/content/repositories/maven-064/ > https://repository.apache.org/content/repositories/maven-064/org/apache/maven/shared/maven-jarsigner/1.2/maven-jarsigner-1.2-source-release.zip > > Source release checksum(s): > maven-jarsigner-1.2-source-release.zip sha1: > 573fa9d50cc08bd65a2bf0d077e6c1b08d70046b > > Staging site: > http://maven.apache.org/shared-archives/maven-jarsigner-LATEST/ > > Guide to testing staged releases: > http://maven.apache.org/guides/development/guide-testing-releases.html > > Vote open for 72 hours. > > [ ] +1 > [ ] +0 > [ ] -1 > > my +1 > > tony. > -- Tony Chemit tél: +33 (0) 2 40 50 29 28 http://www.codelutin.com email: che...@codelutin.com twitter: https://twitter.com/tchemit - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Plugin phase awareness...
Something like this should do the trick
@Parameter(defaultValue = "${mojoExecution.lifecyclePhase}")
private String executionPhase;
other "magic" properties available to mojos are documented in [1]
[1]
http://maven.apache.org/ref/3.1.1/maven-core/apidocs/org/apache/maven/plugin/PluginParameterExpressionEvaluator.html
--
Regards,
Igor
On 12/21/2013, 3:52, Lennart Jörelid wrote:
Hello all,
How can a running Mojo query the Maven API (or some other API) to find out
which Maven Phase it has been invoked in? Something like ...
String currentPhase = getSomeMavenApiHelper().getCurrentPhase();
--
+==+
| Bästa hälsningar,
| [sw. "Best regards"]
|
| Lennart Jörelid
| EAI Architect & Integrator
|
| jGuru Europe AB
| Mölnlycke - Kista
|
| Email: l...@jguru.se
| URL: www.jguru.se
| Phone
| (skype):jgurueurope
| (intl): +46 708 507 603
| (domestic): 0708 - 507 603
+==+
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
RE: Plugin phase awareness...
bash>mvn help:effective-pom | grep phase site-deploy package generate-resources site site-deploy test test-compile compile clean install process-resources process-test-resources package deploy ? Martin __ Inte förändra och störa detta meddelande > Date: Sat, 21 Dec 2013 09:52:56 +0100 > Subject: Plugin phase awareness... > From: lennart.jore...@gmail.com > To: dev@maven.apache.org > > Hello all, > > How can a running Mojo query the Maven API (or some other API) to find out > which Maven Phase it has been invoked in? Something like ... > > String currentPhase = getSomeMavenApiHelper().getCurrentPhase(); > > -- > +==+ > | Bästa hälsningar, > | [sw. "Best regards"] > | > | Lennart Jörelid > | EAI Architect & Integrator > | > | jGuru Europe AB > | Mölnlycke - Kista > | > | Email: l...@jguru.se > | URL: www.jguru.se > | Phone > | (skype): jgurueurope > | (intl): +46 708 507 603 > | (domestic): 0708 - 507 603 > +==+
Re: New logo?
Having thought about it overnight... if people really want to go with a non-stylised raven we can always ask for permission: http://people.apache.org/~stephenc/maven-logo-contest/maven-9.png OTOH here is a different stylised version http://people.apache.org/~stephenc/maven-logo-contest/maven-10.png Finally, here is a raven totem http://people.apache.org/~stephenc/maven-logo-contest/maven-11.png I think this last one could be put in a forest with sky background... just haven't had time to do it On 20 December 2013 22:26, Stephen Connolly wrote: > I think we can't go with the raven > > http://www.prweb.com/releases/2012/3/prweb9334175.htm > > Given that a different non-competing user of the name is using a raven in > their logo > > On Friday, 20 December 2013, Manfred Moser wrote: > >> > >> > On Dec 20, 2013, at 1:01 PM, Manfred Moser >> > wrote: >> > >> >> I would move the Raven closer to the word Maven but otherwise this >> looks >> >> good imho. Of course I am not sure if everyone would recognize it as a >> >> raven .. >> > >> > That’s my problem…. doesn’t look like a raven to me at all. >> > >> > When I first looked at it, I guess the “mouth + tough” part seemed to >> look >> > more like the Seattle SeaHawks logo stuck on a boot with a weird swirly >> > thing at the ankle. >> > >> > In other words, a little to “abstract” for me. :-) >> >> Fair enough. I guess living in the pacific northwest I am exposed to these >> depictions a lot so I can tell. But globally we might have to make it a >> bit clearer. Good input ;-) >> >> manfred >> >> - >> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org >> For additional commands, e-mail: dev-h...@maven.apache.org >> >> > > -- > Sent from my phone >
Plugin phase awareness...
Hello all, How can a running Mojo query the Maven API (or some other API) to find out which Maven Phase it has been invoked in? Something like ... String currentPhase = getSomeMavenApiHelper().getCurrentPhase(); -- +==+ | Bästa hälsningar, | [sw. "Best regards"] | | Lennart Jörelid | EAI Architect & Integrator | | jGuru Europe AB | Mölnlycke - Kista | | Email: l...@jguru.se | URL: www.jguru.se | Phone | (skype):jgurueurope | (intl): +46 708 507 603 | (domestic): 0708 - 507 603 +==+
