[jira] Created: (MSITE-429) Add Galician locale (gl) support
Add Galician locale (gl) support Key: MSITE-429 URL: http://jira.codehaus.org/browse/MSITE-429 Project: Maven 2.x Site Plugin Issue Type: Improvement Components: internationalization Affects Versions: 2.0.1 Reporter: Daniel Fernández Attachments: project-info-report_gl.properties, site-plugin_gl.properties, site-tool_gl.properties Galician locales (gl, gl_ES), which apply to one of the four official languages of Spain (and native to more than 3 million people), are not supported out-of-the-box by Sun's Java Virtual Machine, but it can be added as a JVM extension, as you can read in http://www.javagalician.org Attached are the files to add Galician (gl) support to the Maven Site Plugin in order to be able to create maven sites in Galician language. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MASSEMBLY-446) apache-source-release-assembly DOES NOT exclude target/** in maven-remote-resources-plugin build
[
http://jira.codehaus.org/browse/MASSEMBLY-446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=191643#action_191643
]
Benjamin Bentmann commented on MASSEMBLY-446:
-
Possibly due to paths like
{{target/test-classes/unit/test-dir/default-createbundle/src/main/...}}.
> apache-source-release-assembly DOES NOT exclude target/** in
> maven-remote-resources-plugin build
>
>
> Key: MASSEMBLY-446
> URL: http://jira.codehaus.org/browse/MASSEMBLY-446
> Project: Maven 2.x Assembly Plugin
> Issue Type: Bug
>Affects Versions: 2.2-beta-4
>Reporter: John Casey
> Fix For: 2.2-beta-5
>
>
> Need to investigate why target/** isn't excluded from the source-release zip.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MDEP-234) Make the list and tree mojos support listing transitive dependencies for war artifact types
Make the list and tree mojos support listing transitive dependencies for war
artifact types
---
Key: MDEP-234
URL: http://jira.codehaus.org/browse/MDEP-234
Project: Maven 2.x Dependency Plugin
Issue Type: Improvement
Components: tree
Affects Versions: 2.1
Reporter: Vincent Massol
Assignee: Brian Fox
For example, check out
http://svn.xwiki.org/svnroot/xwiki/enterprise/trunk/web/
(note: you'll need to specify the xwiki remote repo in your settings.xml as
mentioned here:
http://dev.xwiki.org/xwiki/bin/view/Community/Building#HInstallingMaven )
When you runt "mvn dependency:tree" (or dependency:list) you get:
{noformat}
[INFO] [dependency:tree {execution: default-cli}]
[INFO] com.xpn.xwiki.products:xwiki-enterprise-web:war:2.1-SNAPSHOT
[INFO] +- com.xpn.xwiki.platform:xwiki-web-standard:war:2.1-SNAPSHOT:compile
[INFO] +-
com.xpn.xwiki.platform.plugins:xwiki-plugin-watchlist:jar:1.20-SNAPSHOT:compile
[INFO] +-
com.xpn.xwiki.platform.plugins:xwiki-plugin-jodatime:jar:1.4-SNAPSHOT:compile
...
{noformat}
As you can see the com.xpn.xwiki.platform:xwiki-web-standard:war dependency
doesn't contain any transitive deps but it has several of them
(see http://svn.xwiki.org/svnroot/xwiki/platform/web/trunk/standard/pom.xml )
This is probably because the general artifact resolver stops at WAR packaging
types. While this is probably fine when executing a maven project, it isn't
when listing all project dependencies.
Thanks
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MAVENUPLOAD-2578) Sync with datanucleus M2 repo
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=191651#action_191651 ] David J. M. Karlsen commented on MAVENUPLOAD-2578: -- This seems to be broken: Central has 1.0.1: http://repo2.maven.org/maven2/org/datanucleus/datanucleus-cache/ The latest in the source repo is 1.1.1: http://www.datanucleus.org/downloads/maven2/org/datanucleus/datanucleus-cache/ > Sync with datanucleus M2 repo > - > > Key: MAVENUPLOAD-2578 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2578 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Data Nucleus >Assignee: Carlos Sanchez > > "org.datanucleus","j...@www.datanucleus.org:/home/jpox/htdocs/downloads/maven2","rsync_ssh","Andy > Jefferson","i...@datanucleus.org",, > The domain is obviously mine, registered under my name. > I put the Maven public key into the user "jpox" "$home/.ssh/authorized_keys" > Left as an exercise to see if that works -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MAVENUPLOAD-2608) CLONE -Sync with datanucleus M2 repo
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=191652#action_191652 ] David J. M. Karlsen commented on MAVENUPLOAD-2608: -- Reopened since the syncing doesn't seem to work. > CLONE -Sync with datanucleus M2 repo > > > Key: MAVENUPLOAD-2608 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2608 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: David J. M. Karlsen >Assignee: Carlos Sanchez > > "org.datanucleus","j...@www.datanucleus.org:/home/jpox/htdocs/downloads/maven2","rsync_ssh","Andy > Jefferson","i...@datanucleus.org",, > The domain is obviously mine, registered under my name. > I put the Maven public key into the user "jpox" "$home/.ssh/authorized_keys" > Left as an exercise to see if that works -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MAVENUPLOAD-2608) CLONE -Sync with datanucleus M2 repo
CLONE -Sync with datanucleus M2 repo Key: MAVENUPLOAD-2608 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2608 Project: Maven Upload Requests Issue Type: Wish Reporter: David J. M. Karlsen Assignee: Carlos Sanchez "org.datanucleus","j...@www.datanucleus.org:/home/jpox/htdocs/downloads/maven2","rsync_ssh","Andy Jefferson","i...@datanucleus.org",, The domain is obviously mine, registered under my name. I put the Maven public key into the user "jpox" "$home/.ssh/authorized_keys" Left as an exercise to see if that works -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MJARSIGNER-7) jarsigner plugin to support all "types" of zip files
[
http://jira.codehaus.org/browse/MJARSIGNER-7?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann closed MJARSIGNER-7.
--
Assignee: Benjamin Bentmann
Resolution: Fixed
Fix Version/s: 1.2
Done in [r817056|http://svn.apache.org/viewvc?view=rev&revision=817056].
> jarsigner plugin to support all "types" of zip files
>
>
> Key: MJARSIGNER-7
> URL: http://jira.codehaus.org/browse/MJARSIGNER-7
> Project: Maven 2.x Jar Signer Plugin
> Issue Type: Wish
>Affects Versions: 1.1
> Environment: all
>Reporter: Martin Scholl
>Assignee: Benjamin Bentmann
>Priority: Minor
> Fix For: 1.2
>
>
> It would be great if the jarsigner plugin was able to sign all zip files, not
> only those which contain a META-INF folder and/or jar files as the jarsigner
> command line tool is not limited to "real" jar files. The META-INF folder is
> created anyway by the jarsigner tool.
> My usecase is that I have some projects that create attached zip assemblies
> and I would like to sign them, too. I don't want to use e.g. an additional
> ant task attached to the verification phase, as the signing should be done
> automatically imho. And I don't want to use "external" signing tools like gpg
> as it requires a manual installation of that tool whereas the jarsigner is
> always present (in a JDK).
> Simply replace the isJarFile method like that or similar:
> private boolean isZipFile( final File file )
> {
> try
> {
> // NOTE: ZipFile.getEntry() might be shorter but is several
> factors slower on large files
> ZipInputStream zis = new ZipInputStream( new FileInputStream(
> file ) );
> try
> {
> return zis.available() == 1;
> }
> finally
> {
> zis.close();
> }
> }
> catch ( Exception e )
> {
> // ignore, will fail below
> }
> return false;
> }
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MJARSIGNER-8) Allow to exclude specific attachments from signing/verification
Allow to exclude specific attachments from signing/verification --- Key: MJARSIGNER-8 URL: http://jira.codehaus.org/browse/MJARSIGNER-8 Project: Maven 2.x Jar Signer Plugin Issue Type: New Feature Affects Versions: 1.1 Reporter: Benjamin Bentmann While MJARSIGNER-7 presented a use case to sign ordinary ZIPs, there can as well be cases where this is not intended. To make this controllable, the plugin should support to select specific attachments. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MJARSIGNER-8) Allow to exclude specific attachments from signing/verification
[ http://jira.codehaus.org/browse/MJARSIGNER-8?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann closed MJARSIGNER-8. -- Assignee: Benjamin Bentmann Resolution: Fixed Fix Version/s: 1.2 Added excludeClassifiers/includeClassifiers in [r817065|http://svn.apache.org/viewvc?view=rev&revision=817065]. > Allow to exclude specific attachments from signing/verification > --- > > Key: MJARSIGNER-8 > URL: http://jira.codehaus.org/browse/MJARSIGNER-8 > Project: Maven 2.x Jar Signer Plugin > Issue Type: New Feature >Affects Versions: 1.1 >Reporter: Benjamin Bentmann >Assignee: Benjamin Bentmann > Fix For: 1.2 > > > While MJARSIGNER-7 presented a use case to sign ordinary ZIPs, there can as > well be cases where this is not intended. To make this controllable, the > plugin should support to select specific attachments. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MAVENUPLOAD-2608) CLONE -Sync with datanucleus M2 repo
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-2608. --- Resolution: Fixed > CLONE -Sync with datanucleus M2 repo > > > Key: MAVENUPLOAD-2608 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2608 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: David J. M. Karlsen >Assignee: Carlos Sanchez > > "org.datanucleus","j...@www.datanucleus.org:/home/jpox/htdocs/downloads/maven2","rsync_ssh","Andy > Jefferson","i...@datanucleus.org",, > The domain is obviously mine, registered under my name. > I put the Maven public key into the user "jpox" "$home/.ssh/authorized_keys" > Left as an exercise to see if that works -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-4228) [regression] Authorization failed: Not authorized by proxy.
[ http://jira.codehaus.org/browse/MNG-4228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=191663#action_191663 ] Paul Benedict commented on MNG-4228: FYI, Eclipse 3.6M2 now includes NTLMv2 proxy support: http://download.eclipse.org/eclipse/downloads/drops/S-3.6M2-200909170100/eclipse-news-M2.html Peek at their code and determine if it can be re-used for Maven. > [regression] Authorization failed: Not authorized by proxy. > --- > > Key: MNG-4228 > URL: http://jira.codehaus.org/browse/MNG-4228 > Project: Maven 2 > Issue Type: Bug > Components: Artifacts and Repositories, Settings >Affects Versions: 2.2.0 > Environment: Windows XP, java version "1.6.0_04" >Reporter: Marco Noto >Assignee: John Casey >Priority: Blocker > Fix For: 2.2.1 > > Attachments: NTLMV21.RAR, TestNTLMAuth.java > > > I can not access any external repository using the version 2.2.0. If I go > back to 2.1.0 everything works properly. > For example: > mvn -U eclipse:eclipse > [INFO] Scanning for projects... > [INFO] Searching repository for plugin with prefix: 'eclipse'. > [INFO] org.apache.maven.plugins: checking for updates from central > [WARNING] repository metadata for: 'org.apache.maven.plugins' could not be > retrieved from repository: central due > to an error: Authorization failed: Not authorized by proxy. > [INFO] Repository 'central' will be blacklisted -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
