Re: [VOTE] Release PMD Plugin 2.6
+1 -Lukas On 11/08/2011 07:05 PM, Olivier Lamy wrote: Hello, I'd like to release Apache Maven PMD Plugin 2.6. We fixed 5 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11140version=16437. Staging repository: https://repository.apache.org/content/repositories/maven-169/ Staging site: http://maven.apache.org/plugins/maven-pmd-plugin-2.6 (wait sync) Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Vote open for 72H. Here my +1 Thanks, - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Meta information about dependencies in a pom?
On 11/09/2011 12:00 AM, Jason van Zyl wrote:
today we learned about the AbstractMavenLifecycleParticipant
Here's an example of how it works for matching the dependencies specified from
a 3rd party source to the reactor.
[...]
It's using JSR330, but you can pull those out and use Plexus annotations if you
need it to work in the short term.
A standalone example I just got to work: create a jar-packaging project with
@Component(role=AbstractMavenLifecycleParticipant.class)
public class WhateverNameYouLike extends AbstractMavenLifecycleParticipant {
@Requirement private Logger log;
@Override public void afterProjectsRead(MavenSession session) throws
MavenExecutionException {
for (MavenProject p : session.getProjects()) {
log.info(tweaking + p);
Dependency d = new Dependency();
d.setGroupId(org.apache.commons);
d.setArtifactId(commons-io);
d.setVersion(1.3.2);
p.getDependencies().add(d);
}
}
}
built with
build
plugins
plugin
groupIdorg.codehaus.plexus/groupId
artifactIdplexus-component-metadata/artifactId
version1.5.5/version
executions
execution
goals
goalgenerate-metadata/goal
/goals
idgenerate-metadata/id
/execution
/executions
/plugin
/plugins
/build
dependencies
dependency
groupIdorg.apache.maven/groupId
artifactIdmaven-core/artifactId
version3.0.3/version
/dependency
/dependencies
Now create a quickstart project and edit the main method to say:
System.out.println(org.apache.commons.io.EndianUtils.swapInteger(1));
Once you tell it
build
extensions
extension
...coordinates as for first project...
/extension
/extensions
/build
then it will compile (under 3.0.3) despite not itself declaring a dep on
commons-io.
BTW I was not successful in using @javax.inject.Singleton in place of
@Component.
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
RE: [jira] Commented: (MNG-5195) ERROR: JAVA_HOME is set to an invalid directory.
JAVA_HOME should point to C:\GigaSpacesTraining\JDK\jdk1.6.0_24-64\jdk1.6.0_24 (you seem to have an extra subdirectory) -Robert Date: Wed, 9 Nov 2011 11:35:51 -0600 From: j...@codehaus.org To: iss...@maven.apache.org Subject: [jira] Commented: (MNG-5195) ERROR: JAVA_HOME is set to an invalid directory. [ https://jira.codehaus.org/browse/MNG-5195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=283140#comment-283140 ] Dennis Lundberg commented on MNG-5195: -- If you run set from a command prompt, what value does it show for JAVA_HOME? ERROR: JAVA_HOME is set to an invalid directory. Key: MNG-5195 URL: https://jira.codehaus.org/browse/MNG-5195 Project: Maven 2 3 Issue Type: Bug Environment: window 7 Reporter: wangfaxi ERROR: JAVA_HOME is set to an invalid directory. JAVA_HOME = ..\..\..\\JDK\jdk1.6.0_24-64 Please set the JAVA_HOME variable in your environment to match the location of your Java installation My JAVA_HOME is set perfectly ( i checked java.exe set on C:\GigaSpacesTraining\JDK\jdk1.6.0_24-64\jdk1.6.0_24\bin) JAI and JMF all working ... javac and rest of the commands also work so i guess i good with it. any Idea's ? -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Meta information about dependencies in a pom?
Yes that's why I said to pull them out. You won't be successful in using
JSR330. It only works in Tesla, most of which will be integrated back into
Maven. Just haven't had time to post to the dev list yet. JSR330 and
@Injectable SLF4J loggers are but a few of a things possible with code that
exists the Tesla repo.
But it would be easy enough to build that out as a helper where someone just
needs to define the source of their GAs they want to contribute and let the
helper take care of the rest.
On Nov 9, 2011, at 7:57 AM, Jesse Glick wrote:
On 11/09/2011 12:00 AM, Jason van Zyl wrote:
today we learned about the AbstractMavenLifecycleParticipant
Here's an example of how it works for matching the dependencies specified
from a 3rd party source to the reactor.
[...]
It's using JSR330, but you can pull those out and use Plexus annotations if
you need it to work in the short term.
A standalone example I just got to work: create a jar-packaging project with
@Component(role=AbstractMavenLifecycleParticipant.class)
public class WhateverNameYouLike extends AbstractMavenLifecycleParticipant {
@Requirement private Logger log;
@Override public void afterProjectsRead(MavenSession session) throws
MavenExecutionException {
for (MavenProject p : session.getProjects()) {
log.info(tweaking + p);
Dependency d = new Dependency();
d.setGroupId(org.apache.commons);
d.setArtifactId(commons-io);
d.setVersion(1.3.2);
p.getDependencies().add(d);
}
}
}
built with
build
plugins
plugin
groupIdorg.codehaus.plexus/groupId
artifactIdplexus-component-metadata/artifactId
version1.5.5/version
executions
execution
goals
goalgenerate-metadata/goal
/goals
idgenerate-metadata/id
/execution
/executions
/plugin
/plugins
/build
dependencies
dependency
groupIdorg.apache.maven/groupId
artifactIdmaven-core/artifactId
version3.0.3/version
/dependency
/dependencies
Now create a quickstart project and edit the main method to say:
System.out.println(org.apache.commons.io.EndianUtils.swapInteger(1));
Once you tell it
build
extensions
extension
...coordinates as for first project...
/extension
/extensions
/build
then it will compile (under 3.0.3) despite not itself declaring a dep on
commons-io.
BTW I was not successful in using @javax.inject.Singleton in place of
@Component.
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
Thanks,
Jason
--
Jason van Zyl
Founder, Apache Maven
http://twitter.com/jvanzyl
-
What matters is not ideas, but the people who have them. Good people can fix
bad ideas, but good ideas can't save bad people.
-- Paul Graham
