[jira] Created: (SCM-348) missing scm:bootstrap in overview
missing scm:bootstrap in overview - Key: SCM-348 URL: http://jira.codehaus.org/browse/SCM-348 Project: Maven SCM Issue Type: Improvement Components: documentation Reporter: Tomasz Pik Overview on http://maven.apache.org/scm/plugins/index.html page lists most of mojos but list do not include scm:bootstrap. Please, add bootstrap to list. -- 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: (MWAR-122) tests failing in trunk on windows
tests failing in trunk on windows
-
Key: MWAR-122
URL: http://jira.codehaus.org/browse/MWAR-122
Project: Maven 2.x War Plugin
Issue Type: Bug
Affects Versions: 2.1-alpha-1
Environment: WindowsXP
Reporter: Tomasz Pik
Two tests from trunk failing on windows:
Failed tests:
testOverlaysIncludesExcludesWithMultipleDefinitions(org.apache.maven.plugin.war.WarOverlaysTest)
testOverlaysIncludesExcludesWithMultipleDefinitions2(org.apache.maven.plugin.war.WarOverlaysTest)
this is causes by hardcoded META-INF/MAINFEST.MF paths in tests.
File.separator should be used instead of "/" :
-final FileFilter filter = new FileFilterImpl( webAppDirectory, new
String[]{"META-INF/MANIFEST.MF"} );
+ final FileFilter filter = new FileFilterImpl( webAppDirectory, new
String[]{"META-INF" + File.separator + "MANIFEST.MF"} );
--
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-1753) Upload Joda-Time hibernate 1.0
Upload Joda-Time hibernate 1.0 -- Key: MAVENUPLOAD-1753 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1753 Project: maven-upload-requests Issue Type: Improvement Reporter: Stephen Colebourne http://joda-time.sourceforge.net/contrib/hibernate/joda-time-hibernate-1.0-bundle.jar http://joda-time.sourceforge.net/contrib/hibernate/index.html http://joda-time.sourceforge.net/contrib/hibernate/team-list.html Please upload the new joda-time-hibernate release. Thanks. Stephen -- 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: (MJAVADOC-154) Bump to plexus-utils:1.4.6
Bump to plexus-utils:1.4.6 -- Key: MJAVADOC-154 URL: http://jira.codehaus.org/browse/MJAVADOC-154 Project: Maven 2.x Javadoc Plugin Issue Type: Task Affects Versions: 2.3 Reporter: Vincent Siveton -- 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] Updated: (MJAVADOC-154) Bump to plexus-utils:1.4.6
[ http://jira.codehaus.org/browse/MJAVADOC-154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton updated MJAVADOC-154: - Affects Version/s: (was: 2.3) 2.4 Fix Version/s: 2.4 > Bump to plexus-utils:1.4.6 > -- > > Key: MJAVADOC-154 > URL: http://jira.codehaus.org/browse/MJAVADOC-154 > Project: Maven 2.x Javadoc Plugin > Issue Type: Task >Affects Versions: 2.4 >Reporter: Vincent Siveton > Fix For: 2.4 > > -- 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: (MJAVADOC-154) Bump to plexus-utils:1.4.6
[ http://jira.codehaus.org/browse/MJAVADOC-154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton closed MJAVADOC-154. Assignee: Vincent Siveton Resolution: Fixed done in r582623 > Bump to plexus-utils:1.4.6 > -- > > Key: MJAVADOC-154 > URL: http://jira.codehaus.org/browse/MJAVADOC-154 > Project: Maven 2.x Javadoc Plugin > Issue Type: Task >Affects Versions: 2.4 >Reporter: Vincent Siveton >Assignee: Vincent Siveton > Fix For: 2.4 > > -- 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: (CONTINUUM-1514) Legend is hardcoded
Legend is hardcoded --- Key: CONTINUUM-1514 URL: http://jira.codehaus.org/browse/CONTINUUM-1514 Project: Continuum Issue Type: Improvement Components: Web - UI Affects Versions: 1.1-beta-3 Reporter: George Gastaldi Priority: Trivial The legend is hardcoded (\continuum-webapp\src\main\webapp\WEB-INF\jsp\navigations\Menu.jsp). Strings as "Build Now", etc should be moved to continuum.properties. -- 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: (MWAR-122) tests failing in trunk on windows
[
http://jira.codehaus.org/browse/MWAR-122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephane Nicoll closed MWAR-122.
Resolution: Fixed
Fix Version/s: 2.1-alpha-1
Fixed, thanks for the bug hunting.
> tests failing in trunk on windows
> -
>
> Key: MWAR-122
> URL: http://jira.codehaus.org/browse/MWAR-122
> Project: Maven 2.x War Plugin
> Issue Type: Bug
>Affects Versions: 2.1-alpha-1
> Environment: WindowsXP
>Reporter: Tomasz Pik
>Assignee: Stephane Nicoll
> Fix For: 2.1-alpha-1
>
>
> Two tests from trunk failing on windows:
> Failed tests:
>
> testOverlaysIncludesExcludesWithMultipleDefinitions(org.apache.maven.plugin.war.WarOverlaysTest)
>
> testOverlaysIncludesExcludesWithMultipleDefinitions2(org.apache.maven.plugin.war.WarOverlaysTest)
> this is causes by hardcoded META-INF/MAINFEST.MF paths in tests.
> File.separator should be used instead of "/" :
> -final FileFilter filter = new FileFilterImpl( webAppDirectory,
> new String[]{"META-INF/MANIFEST.MF"} );
> + final FileFilter filter = new FileFilterImpl( webAppDirectory,
> new String[]{"META-INF" + File.separator + "MANIFEST.MF"} );
--
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] Updated: (MWAR-119) Update plexus-utils to 1.2
[ http://jira.codehaus.org/browse/MWAR-119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephane Nicoll updated MWAR-119: - Fix Version/s: 2.1-alpha-1 > Update plexus-utils to 1.2 > -- > > Key: MWAR-119 > URL: http://jira.codehaus.org/browse/MWAR-119 > Project: Maven 2.x War Plugin > Issue Type: Improvement >Affects Versions: 2.0.2 >Reporter: Aaron Digulla >Assignee: Stephane Nicoll > Fix For: 2.1-alpha-1 > > > Please update plexus-utils to 1.2 (see > [http://jira.codehaus.org/browse/MRESOURCES-10]). -- 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: (MWAR-113) The ability to not package the actual war file
[ http://jira.codehaus.org/browse/MWAR-113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_109239 ] Stephane Nicoll commented on MWAR-113: -- why don't you call war:exploded? It does exactly that right? > The ability to not package the actual war file > -- > > Key: MWAR-113 > URL: http://jira.codehaus.org/browse/MWAR-113 > Project: Maven 2.x War Plugin > Issue Type: New Feature >Affects Versions: 2.1-alpha-1 > Environment: All >Reporter: Bård Dybwad Kristensen >Priority: Minor > Attachments: maven-war-plugin-2.1-alpha-1-WIN-sources.jar > > > My project uses jetty to run the web-application we package with Maven. Jetty > uses the exploded version of the war, and the war file itself is not needed > (not until we deploy on a Weblogic server, which will be done in system test > and prod). But the developers does not need the war file. The war file itself > is quite large (~70 Mb) and the packaging of the file takes quite a bit of > time. This is unnecessary. So I made a small fix in the plug-in to solve this > problem. I added a new parameter "packageWar" witth getters and setters in > AbstractWarMojo, and did some refactoring in the WarMojo so that the > packaging is only done if this parameter is set to true. > I have added the code with the issue. Some tests fail with this new fix as > they expect the war to be created. I have not altered any tests or added any > tests. Just attaching the code and hope you guys think this is a good idea > that should be included in some future release. The fix saves approx 30 > seconds up to a minute in our projects build cycle. -- 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: (MWAR-109) Problem using webResources in configuration
[ http://jira.codehaus.org/browse/MWAR-109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_109240 ] Stephane Nicoll commented on MWAR-109: -- This is due to the filtering, there's probably a chicken-and-egg problem with the interpolation. Can you please provide the token's values and the tokens in your resources file? > Problem using webResources in configuration > --- > > Key: MWAR-109 > URL: http://jira.codehaus.org/browse/MWAR-109 > Project: Maven 2.x War Plugin > Issue Type: Bug >Affects Versions: 2.0.2, 2.1-alpha-1 >Reporter: David Castro > > I have been trying to get web resources into a resources directory where I > can have them copied over during packaging and filtered as necessary. With > 2.0 the targetPath doesn't work. And with 2.0.2 and 2.0.3-SNAPSHOT I can't > seem to configure without it blowing up at all. They both die at the > IOUtil.copy call in AbstractWarMojo > org.apache.maven.plugin.war.AbstractWarMojo.copyFilteredFile(AbstractWarMojo.java:921) > --- > > org.apache.maven.plugins > maven-war-plugin > 2.0.2 > > > > WEB-INF/spring > true > src/main/resources/WEB-INF/spring > > *.xml > *.properties > > > > > > --- > [INFO] Copy webapp webResources to > /home/arimus/workspace-ym/ym/ym-proj/ym-web/target/myapp > [INFO] > > [ERROR] FATAL ERROR > [INFO] > > [INFO] org.apache.maven.project.MavenProject cannot be cast to > java.lang.String > [INFO] > > [INFO] Trace > java.lang.ClassCastException: org.apache.maven.project.MavenProject cannot be > cast to java.lang.String > at > org.codehaus.plexus.util.InterpolationFilterReader.read(InterpolationFilterReader.java:269) > at > org.codehaus.plexus.util.InterpolationFilterReader.read(InterpolationFilterReader.java:201) > at > org.codehaus.plexus.util.InterpolationFilterReader.read(InterpolationFilterReader.java:162) > at java.io.Reader.read(Reader.java:123) > at org.codehaus.plexus.util.IOUtil.copy(IOUtil.java:212) > at org.codehaus.plexus.util.IOUtil.copy(IOUtil.java:200) > at > org.apache.maven.plugin.war.AbstractWarMojo.copyFilteredFile(AbstractWarMojo.java:921) > at > org.apache.maven.plugin.war.AbstractWarMojo.copyResources(AbstractWarMojo.java:415) > at > org.apache.maven.plugin.war.AbstractWarMojo.buildWebapp(AbstractWarMojo.java:518) > at > org.apache.maven.plugin.war.AbstractWarMojo.buildExplodedWebapp(AbstractWarMojo.java:347) > at > org.apache.maven.plugin.war.WarMojo.performPackaging(WarMojo.java:164) > at org.apache.maven.plugin.war.WarMojo.execute(WarMojo.java:130) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:443) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:480) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:459) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:272) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) > at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) > at > org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) > at org.codehaus.classworlds.Launcher.main(Launcher.java:375) -- This message is automatically generated by JIRA. - If you think it was sent incorrectl
[jira] Updated: (MEAR-75) Incorrect file name in class path (in manifest) if specifying different bundleFileName for module
[
http://jira.codehaus.org/browse/MEAR-75?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephane Nicoll updated MEAR-75:
Priority: Minor (was: Major)
> Incorrect file name in class path (in manifest) if specifying different
> bundleFileName for module
> -
>
> Key: MEAR-75
> URL: http://jira.codehaus.org/browse/MEAR-75
> Project: Maven 2.x Ear Plugin
> Issue Type: Bug
>Affects Versions: 2.3.1
> Environment: Windows XP SP2, Maven 2.0.7, JDK 1.5.0_12
>Reporter: Anders Hammar
>Priority: Minor
> Attachments: jbossaop-poc.zip
>
>
> The file name included in the class path in the generated Manifest.mf file is
> incorrect if a different bundle file name is defined in the configuration for
> the ear plugin. The file name used in the class path is the original file
> name, not the defined bundle file name (which is the actual file name in the
> created ear).
> In my POM I have:
> {code:title=pom.xml|borderStyle=solid}
> ...
>
>
> jbossaop-poc
> aop
> jar
>
> ...
>
>
>
>
> maven-ear-plugin
>
>
>
>
> true
>
>
>
>
>
> jbossaop-poc
>
> aop
>
> aop-${pom.version}.aop
>
> true
>
>
>
>
>
>
> {code}
> In the resulting ear file, the included artifact 'aop-1.0-SNAPSHOT.jar' has
> been renamed to 'aop-1.0-SNAPSHOT.aop'. However, in the Manifest.mf (in the
> ear) the class path incorrectly specifies:
> Class-Path: aop-1.0-SNAPSHOT.jar
> Attached is a multi-module project that should reproduce this.
--
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-1754) Uploading proguard 4.0 to The Central Repository
Uploading proguard 4.0 to The Central Repository Key: MAVENUPLOAD-1754 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1754 Project: maven-upload-requests Issue Type: Task Reporter: Vlad Skarzhevskyy Please Upload the latest version to Repository. The last version (posted by me) in repository is 3.10 http://pyx4j.com/downloads/proguard-4.0-bundle.jar http://proguard.sourceforge.net/ ProGuard is a free Java class file shrinker, optimizer, and obfuscator. It removes unused classes, fields, methods, and attributes. It then optimizes the bytecode. It then renames the remaining classes, fields, and methods using short meaningless names. Version 4.0 * Added preverifier for Java 6 and Java Micro Edition, with new options -microedition and -dontpreverify. * Added new option -target to modify java version of processed class files. * Made -keep options more orthogonal and flexible, with option modifiers allowshrinking, allowoptimization, and allowobfuscation. * Added new wildcards for class member descriptors: "***", matching any type, and "...", matching any number of arguments. * Added support for configuration by means of annotations. * Improved shrinking of unused annotations. * Added check on modification times of input and output, to avoid unnecessary processing, with new option -forceprocessing. * Added new options -flattenpackagehierarchy and -repackageclasses (replacing -defaultpackage) to control obfuscation of package names. * Added new options -adaptresourcefilenames and -adaptresourcefilecontents, with file filters, to update resource files corresponding to obfuscated class names. * Added detection of dynamically accessed fields and methods. * Now treating Exceptions attributes as optional. * Now respecting naming rule for nested class names (EnclosingClass$InnerClass) in obfuscation step, if InnerClasses attributes or EnclosingMethod attributes are being kept. * Added new inter-procedural optimizations: method inlining and propagation of constant fields, constant arguments, and constant return values. * Added optimized local variable allocation. * Added over 250 new peephole optimizations. * Improved making classes and class members public or protected. * Now printing notes on suspiciously unkept classes in parameters of specified methods. * Now printing notes for class names that don't seem to be fully qualified. * Added support for uppercase filename extensions. * Added tool tips to the GUI. * Rewritten class file I/O code. * Updated documentation and examples. -- 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-1755) Extratags version 1.0.2
Extratags version 1.0.2 --- Key: MAVENUPLOAD-1755 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1755 Project: maven-upload-requests Issue Type: Task Reporter: Tom Schneider Attachments: extratags-1.0.2-bundle.jar http://extratags.googlecode.com/files/extratags-1.0.2-bundle.jar http://code.google.com/p/extratags/ http://cwiki.apache.org/S2PLUGINS/extratags-plugin.html ExtraTags is a set of additional UI tags for struts2. -- 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: (MWAR-123) filtering with @ is working randomly
filtering with @ is working randomly
Key: MWAR-123
URL: http://jira.codehaus.org/browse/MWAR-123
Project: Maven 2.x War Plugin
Issue Type: Bug
Affects Versions: 2.1-alpha-1
Reporter: Tomasz Pik
Attachments: filters.patch
Attached patch adding testing for filtering using @...@ (in parallel with
filtering using ${..}) tokens.
However, if you'll change
# this is comment created by author at somewhere
to
# this is comment created by [EMAIL PROTECTED]"
then test case will fall.
As far as I know this problem has a root in plexus utils but this is very
important for filtering jsp files (and so - for maven-war-plugin) because @
character has a special meaning in jsp.
So adding a directive like <%@ page import="package" %> will effectively
'disable' filtering.
--
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: (MWAR-113) The ability to not package the actual war file
[ http://jira.codehaus.org/browse/MWAR-113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_109244 ] Stephane Nicoll commented on MWAR-113: -- Well, it happens :) No, there's no way to change that, except if you define your own lifecycle. However, I am not sure it's a good idea to do what you're asking. I'll discuss that on the dev list. > The ability to not package the actual war file > -- > > Key: MWAR-113 > URL: http://jira.codehaus.org/browse/MWAR-113 > Project: Maven 2.x War Plugin > Issue Type: New Feature >Affects Versions: 2.1-alpha-1 > Environment: All >Reporter: Bård Dybwad Kristensen >Priority: Minor > Attachments: maven-war-plugin-2.1-alpha-1-WIN-sources.jar > > > My project uses jetty to run the web-application we package with Maven. Jetty > uses the exploded version of the war, and the war file itself is not needed > (not until we deploy on a Weblogic server, which will be done in system test > and prod). But the developers does not need the war file. The war file itself > is quite large (~70 Mb) and the packaging of the file takes quite a bit of > time. This is unnecessary. So I made a small fix in the plug-in to solve this > problem. I added a new parameter "packageWar" witth getters and setters in > AbstractWarMojo, and did some refactoring in the WarMojo so that the > packaging is only done if this parameter is set to true. > I have added the code with the issue. Some tests fail with this new fix as > they expect the war to be created. I have not altered any tests or added any > tests. Just attaching the code and hope you guys think this is a good idea > that should be included in some future release. The fix saves approx 30 > seconds up to a minute in our projects build cycle. -- 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: (MWAR-119) Update plexus-utils to 1.2
[ http://jira.codehaus.org/browse/MWAR-119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephane Nicoll closed MWAR-119. Resolution: Fixed Updated to latest plexus-utils. > Update plexus-utils to 1.2 > -- > > Key: MWAR-119 > URL: http://jira.codehaus.org/browse/MWAR-119 > Project: Maven 2.x War Plugin > Issue Type: Improvement >Affects Versions: 2.0.2 >Reporter: Aaron Digulla >Assignee: Stephane Nicoll > Fix For: 2.1-alpha-1 > > > Please update plexus-utils to 1.2 (see > [http://jira.codehaus.org/browse/MRESOURCES-10]). -- 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: (MWAR-104) handle zip dependencies in war plugin
[ http://jira.codehaus.org/browse/MWAR-104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_109246 ] Stephane Nicoll commented on MWAR-104: -- It will be resolved when I have time or if someone provides a complete patch that I could apply. Sorry guys, but lately I am way too busy to do this. Meanwhile it would be great if you could use/test the plugin as it is now in trunk. The first alpha might break things so I prefer we test right now. > handle zip dependencies in war plugin > - > > Key: MWAR-104 > URL: http://jira.codehaus.org/browse/MWAR-104 > Project: Maven 2.x War Plugin > Issue Type: Improvement > Environment: all >Reporter: Olivier Lamy >Assignee: Stephane Nicoll > Fix For: 2.1-alpha-1 > > Attachments: foobar.zip, MWAR-104 > > > As MNG-1683 has been applied, the zip artifact must be handled in the war > plugin. -- 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] Updated: (MWAR-104) handle zip dependencies in war plugin
[ http://jira.codehaus.org/browse/MWAR-104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy updated MWAR-104: -- Assignee: Olivier Lamy (was: Stephane Nicoll) As I'm reporter of this issue. I can take the point. > handle zip dependencies in war plugin > - > > Key: MWAR-104 > URL: http://jira.codehaus.org/browse/MWAR-104 > Project: Maven 2.x War Plugin > Issue Type: Improvement > Environment: all >Reporter: Olivier Lamy >Assignee: Olivier Lamy > Fix For: 2.1-alpha-1 > > Attachments: foobar.zip, MWAR-104 > > > As MNG-1683 has been applied, the zip artifact must be handled in the war > plugin. -- 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: (DOXIA-158) doxia book with APT verbatim text not monospaced in PDF
[ http://jira.codehaus.org/browse/DOXIA-158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_109249 ] David Roussel commented on DOXIA-158: - Vincent, The iText code you link to looks fine. But if I look in org.apache.maven.doxia.module.itext.ITextSink the verbatim() method doesn't seem to mention monospaced fonts, even though there is an ITextFont.getMonoSpacedFont() method. Infact getMonoSpacedFont() is never called. Ideally we should have a call to font.setMonospaced(true) in verbatim(), and call font.setMonospaced(false) in _verbatim(). David > doxia book with APT verbatim text not monospaced in PDF > --- > > Key: DOXIA-158 > URL: http://jira.codehaus.org/browse/DOXIA-158 > Project: Maven Doxia > Issue Type: Bug > Components: Module - Itext >Affects Versions: 1.0-alpha-9 > Environment: Java 5 on WinXP >Reporter: David Roussel > Attachments: doxia-test.zip > > > I'm using doxia-maven-plugin 1.0-alpha-9 with APT as an imput source. When > I generate xhtml then the verbatim text comes out fine as a pre tag. When I > generate PDF the verbatim text is rendered with a variable width font, thus > my code examples are all over the place. -- 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] Updated: (DOXIA-158) doxia book with APT verbatim text not monospaced in PDF
[ http://jira.codehaus.org/browse/DOXIA-158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Roussel updated DOXIA-158: Attachment: verbatim_font_change.patch I tried this patch. But it didn't seem to fix it. Not sure why? attached: verbatim_font_change.patch > doxia book with APT verbatim text not monospaced in PDF > --- > > Key: DOXIA-158 > URL: http://jira.codehaus.org/browse/DOXIA-158 > Project: Maven Doxia > Issue Type: Bug > Components: Module - Itext >Affects Versions: 1.0-alpha-9 > Environment: Java 5 on WinXP >Reporter: David Roussel > Attachments: doxia-test.zip, verbatim_font_change.patch > > > I'm using doxia-maven-plugin 1.0-alpha-9 with APT as an imput source. When > I generate xhtml then the verbatim text comes out fine as a pre tag. When I > generate PDF the verbatim text is rendered with a variable width font, thus > my code examples are all over the place. -- 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: (MWAR-104) handle zip dependencies in war plugin
[ http://jira.codehaus.org/browse/MWAR-104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy closed MWAR-104. - Resolution: Fixed committed in rev 582696. snapshot deployed : maven-war-plugin-2.1-alpha-1-20071007.232049-2.jar. Stephane can you fix perm rights on maven-metadata.xml (or redeploy the snapshot ?). -rw-r--r-- 1 snicoll apcvs 55535 Aug 12 03:42 maven-war-plugin-2.1-alpha-1-20070812.104230-1.jar -rw-r--r-- 1 snicoll apcvs 32 Aug 12 03:42 maven-war-plugin-2.1-alpha-1-20070812.104230-1.jar.md5 -rw-r--r-- 1 snicoll apcvs 40 Aug 12 03:42 maven-war-plugin-2.1-alpha-1-20070812.104230-1.jar.sha1 -rw-r--r-- 1 snicoll apcvs380 Aug 12 03:43 maven-metadata.xml -rw-r--r-- 1 snicoll apcvs 32 Aug 12 03:43 maven-metadata.xml.md5 -rw-r--r-- 1 snicoll apcvs 40 Aug 12 03:43 maven-metadata.xml.sha1 -rw-r--r-- 1 snicoll apcvs 2683 Aug 12 03:43 maven-war-plugin-2.1-alpha-1-20070812.104230-1.pom -rw-r--r-- 1 snicoll apcvs 32 Aug 12 03:43 maven-war-plugin-2.1-alpha-1-20070812.104230-1.pom.md5 -rw-r--r-- 1 snicoll apcvs 40 Aug 12 03:43 maven-war-plugin-2.1-alpha-1-20070812.104230-1.pom.sha1 -rw-r--r-- 1 olamyapcvs 54105 Oct 7 16:21 maven-war-plugin-2.1-alpha-1-20071007.232049-2.jar -rw-r--r-- 1 olamyapcvs 40 Oct 7 16:21 maven-war-plugin-2.1-alpha-1-20071007.232049-2.jar.sha1 -rw-r--r-- 1 olamyapcvs 32 Oct 7 16:21 maven-war-plugin-2.1-alpha-1-20071007.232049-2.jar.md5 > handle zip dependencies in war plugin > - > > Key: MWAR-104 > URL: http://jira.codehaus.org/browse/MWAR-104 > Project: Maven 2.x War Plugin > Issue Type: Improvement > Environment: all >Reporter: Olivier Lamy >Assignee: Olivier Lamy > Fix For: 2.1-alpha-1 > > Attachments: foobar.zip, MWAR-104 > > > As MNG-1683 has been applied, the zip artifact must be handled in the war > plugin. -- 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-2290) Generated URLs in POMs of child modules
[
http://jira.codehaus.org/browse/MNG-2290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_109252
]
William Ferguson commented on MNG-2290:
---
Joerg,
I've come to the conclusion that while this is definitely an issue that should
be resolved, we are going to deal with it by always exlicitly declaring url and
site#url properties in our POMs to avoid the aberrant childPathAdjustment
mechanism. And I don't believe that anyone else rates it highly enough to be
bothered about fixing it.
So if you still want to close it, no argument from me.
> Generated URLs in POMs of child modules
> ---
>
> Key: MNG-2290
> URL: http://jira.codehaus.org/browse/MNG-2290
> Project: Maven 2
> Issue Type: Improvement
> Components: Inheritance and Interpolation
>Affects Versions: 2.0.4
>Reporter: Joerg Schaible
> Fix For: 2.0.x
>
>
> Maven has quite some elements where a URL or a path is modified automatically
> for child POMs (the ones I am currently aware of):
> - url
> - scm/connection
> - scm/developerConnection
> - scm/url
> - distributionManagement/site/url
> While expanding this path with "/${pom.artifactId}" sounds reasonable, this
> approach fails badly for complex projects with more hierarchy levels. Suppose
> we have a directory structure like:
> * project
> ** core
> *** provider
> commons
> impl1
> In this hierarchy all POMs for _project_, _core_ and _provider_ are of
> package type _pom_, while _commons_ and _impl1_ is of type _jar_. The
> "artifactId" approach now simply assumes that all POMs in the hierarchy are
> named like the current directory. This does simply not match. Suppose those
> jar artifacts are used in an enterprise or web app. Then every artifact is
> located in one single directory and therefore the names have to be unique.
> But if you decide to take an artifact name different to the directory name,
> you have to add the definition in every POM, because the scm elements are
> simply wrong.
> An even worse scenario are components that can be provided using different
> technologies. We have a lot of such structures:
> * component
> ** jar
> ** war
> ** ear
> * *_jar_:* the core functionality
> * *_war_:* the core functionality integrated and eccessible with a web
> application
> * *_ear_:* the complete component as enterprise app, if it makes sense to
> deploy the functionality on a different app server
> _component_ has a POM of package type _pom_; _jar_, _war_ and _ear_ have POMs
> with the according package type. All of the three POMs use the same
> artifactId though. In this case not only the scm elements break, but also the
> URLs for the site, since they are all the same for all three artifacts.
> All of this could have been avoided, if the expanded part is not the
> artifactId, but the basename of the current directory. Especially for the scm
> elements, this is IMHO the only valid assumption.
> It would already help us, if this auto-expansion could be turned off to allow
> the definition of a single property in each POM for a correct interpolation
> of those values, but there seems no such option ^1^. So you *have to* add
> those elements under all circumstances into every POM.
> 1) The _tagBase_ of the release plugin does no such auto-expansion, which
> makes it quite easy to use a property for it, that can be set individually in
> every POM without adding any plugin configuration.
--
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] Updated: (CONTINUUM-1499) Translate to Brazilian Portuguese
[ http://jira.codehaus.org/browse/CONTINUUM-1499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] George Gastaldi updated CONTINUUM-1499: --- Attachment: CONTINUUM-1499-gastaldi-3.patch Another Patch to strings (Better organization and fixes some strings) > Translate to Brazilian Portuguese > - > > Key: CONTINUUM-1499 > URL: http://jira.codehaus.org/browse/CONTINUUM-1499 > Project: Continuum > Issue Type: Sub-task > Components: Web - UI >Reporter: George Gastaldi >Assignee: Olivier Lamy >Priority: Minor > Fix For: 1.1-beta-4 > > Attachments: CONTINUUM-1499-gastaldi-2.patch, > CONTINUUM-1499-gastaldi-3.patch, CONTINUUM-1499-gastaldi.patch > > -- 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] Updated: (CONTINUUM-1514) Legend is hardcoded
[ http://jira.codehaus.org/browse/CONTINUUM-1514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy updated CONTINUUM-1514: Fix Version/s: 1.1-beta-4 > Legend is hardcoded > --- > > Key: CONTINUUM-1514 > URL: http://jira.codehaus.org/browse/CONTINUUM-1514 > Project: Continuum > Issue Type: Improvement > Components: Web - UI >Affects Versions: 1.1-beta-3 >Reporter: George Gastaldi >Priority: Trivial > Fix For: 1.1-beta-4 > > > The legend is hardcoded > (\continuum-webapp\src\main\webapp\WEB-INF\jsp\navigations\Menu.jsp). Strings > as "Build Now", etc should be moved to continuum.properties. -- 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
