Re: Plexus repos moved

2015-02-11 Thread Stephen Connolly
ping: stephenc

On 9 February 2015 at 17:13, Kristian Rosenvold krosenv...@apache.org
wrote:

 They are now all at https://github.com/codehaus-plexus

 The issue tracking should be closed on the sonatype clones, it does
 not seem like it's possible to disable pull requests.

 Any maven devs or existing committers needing permissions should just
 ping. We'll hopefully get maven central access for publishing for
 everyone in the github org. In the meantime, the usual suspects can
 publish to central.

 Kristian

 -
 To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
 For additional commands, e-mail: dev-h...@maven.apache.org




[VOTE] Release Apache Maven PDF Plugin version 1.3

2015-02-11 Thread Karl Heinz Marbaise

Hi,

We solved 9 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11932version=18950

There are still a couple of issues left in JIRA:
http://jira.codehaus.org/issues/?jql=project%20%3D%20MPDF%20AND%20status%20%3D%20Open%20ORDER%20BY%20key%20DESC%2C%20priority%20DESC

Staging repo:
https://repository.apache.org/content/repositories/maven-1137/

https://repository.apache.org/content/repositories/maven-1137/org/apache/maven/plugins/maven-pdf-plugin/1.3/maven-pdf-plugin-1.3-source-release.zip

Source release checksum(s):
maven-pdf-plugin-source-release.zip sha1: 
1e8df80049a3c61d2b899120d700b52670181745


Staging site:
http://maven.apache.org/plugins-archives/maven-pdf-plugin-LATEST/

Guide to testing staged releases:
http://maven.apache.org/guides/development/guide-testing-releases.html

Vote open for 72 hours.

[ ] +1
[ ] +0
[ ] -1

Kind regards
Karl Heinz Marbaise

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org



Re: Plexus repos moved

2015-02-11 Thread Grzegorz SÅ‚owikowski
Hi

I see some strange differences in related repos, for example:

https://github.com/sonatype/plexus-archiver - 45 releases
https://github.com/codehaus-plexus/plexus-archiver - 0 releases

https://github.com/sonatype/plexus-io - 36 releases
https://github.com/codehaus-plexus/plexus-io - 0 releases

https://github.com/sonatype/plexus-interpolation - 25 releases, 165 commits
https://github.com/krosenvold/plexus-interpolation - 2 releases, 168 commits
https://github.com/codehaus-plexus/plexus-interpolation - 2 releases,
166 commits

Regards
Grzegorz Slowikowski

On 2015-02-09 18:13, Kristian Rosenvold wrote:
 They are now all at https://github.com/codehaus-plexus

 The issue tracking should be closed on the sonatype clones, it does
 not seem like it's possible to disable pull requests.

 Any maven devs or existing committers needing permissions should just
 ping. We'll hopefully get maven central access for publishing for
 everyone in the github org. In the meantime, the usual suspects can
 publish to central.

 Kristian

 -
 To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
 For additional commands, e-mail: dev-h...@maven.apache.org




-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org



[GitHub] maven pull request: [MNG-5728] Switch the default checksum policy ...

2015-02-11 Thread njuneau
GitHub user njuneau opened a pull request:

https://github.com/apache/maven/pull/36

[MNG-5728] Switch the default checksum policy from warn to fail

Related to JIRA issue MNG-5728 : https://jira.codehaus.org/browse/MNG-5728 
regarding the default usage of the fail checksum policy.

Puts fail as the default checksum policy, when no -C or -c option
is given in the command line. -C option no longer has any effect, but
has remained in the options for backwards compatibility.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/njuneau/maven MNG-5728

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/maven/pull/36.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #36


commit c4fe46970dbb541692ff8b51e6cf509f1fcc5f79
Author: Nicolas Juneau nicolas.jun...@savoirfairelinux.com
Date:   2015-02-11T20:15:24Z

[MNG-5728] Switch the default checksum policy from warn to fail

Puts fail as the default checksum policy, when no -C or -c option
is given in the command line. -C option no longer has any effect, but
has remained in the options for backwards compatibility.




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org



Classloader issues

2015-02-11 Thread Petar Tahchiev
Hi there,

I have the following maven project setup:

master
| module1
| class ClassA (has annotation @Annotation)
| module2
| class ClassB (also has annotation @Annotation)

and I'm building it with maven, and I use an AbstractProcessor during
compilation to find all types annotated with @Annotation. When I build it
from the module1 level it all works fine. The problem appears when I build
it from master level. Then, what happens is I get an exception that class B
cannot be found.

Caused by: org.reflections.ReflectionsException: could not get type
for name ClassB
at org.reflections.ReflectionUtils.forName(ReflectionUtils.java:389)
at org.reflections.ReflectionUtils.forNames(ReflectionUtils.java:398)
at org.reflections.Reflections.getTypesAnnotatedWith(Reflections.java:385)
at org.reflections.Reflections.getTypesAnnotatedWith(Reflections.java:370)

Here's how I find the types annotated with @Annotation:

 final Reflections reflections =
new Reflections(new
ConfigurationBuilder().setUrls(ClasspathHelper.forClassLoader(ClasspathHelper.staticClassLoader())).setScanners(
new TypeAnnotationsScanner(),
new SubTypesScanner()));
return reflections.getTypesAnnotatedWith(Annotation.class);

What happens is that the classloader will find all the jars in my pom.xml
AND also the following url:

/home/petar/workspace/master/./

and then it will be given to Reflections (method scan on line 235 in
Reflections class ) where it will be treated as a SystemDir so reflections
will recursively go thorough all the subfolders and add all the classes it
finds (which also includes module2/target/classes/ClassB.class). Then it
will try to load it and it will produce the error I pasted above. Now i'm
not sure who's passing the master folder to the classpath, but I checked
the maven classpath with -X and I don't see this folder coming from maven.

Any idea who's adding this folder in the classpath, and also how can I
disable adding it?

Thanks a lot.

-- 
Regards, Petar!
Karlovo, Bulgaria.
---
Public PGP Key at:
https://keyserver1.pgp.com/vkd/DownloadKey.event?keyid=0x19658550C3110611
Key Fingerprint: A369 A7EE 61BC 93A3 CDFF  55A5 1965 8550 C311 0611