[jira] Commented: (MAVENUPLOAD-1972) please upload GWT 1.4.62
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=128308#action_128308 ] nicolas de loof commented on MAVENUPLOAD-1972: -- Right, so please sync com.google.gwt groupId from : "com.google.gwt","[EMAIL PROTECTED]:/home/nicolas/rsync-to-central","rsync_ssh","Nicolas De Loof","[EMAIL PROTECTED]",, > please upload GWT 1.4.62 > > > Key: MAVENUPLOAD-1972 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1972 > Project: maven-upload-requests > Issue Type: Wish >Reporter: nicolas de loof > > Google guys just released GWT 1.4.62 > (http://groups.google.com/group/Google-Web-Toolkit/browse_thread/thread/bd5cbb7a0d5b60aa/b85b6c2157aa26cb) > I'd like to update the codehaus GWT plugin to use this version > The bundle contains server and runtime jars + development jars for windows, > linux, mac and macOS leopard -- 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-131) Ability to deploy the content of WEB-INF/classes as a classified artifact
[ http://jira.codehaus.org/browse/MWAR-131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=128311#action_128311 ] Stephane Nicoll commented on MWAR-131: -- I agree Wendy but in many cases you just don't have the choice. Some users use the technique you mention to have dependency management working with multiple war overlays (till we find an acceptable solution). The problem is the overlay functionality in maven which is not supported properly > Ability to deploy the content of WEB-INF/classes as a classified artifact > - > > Key: MWAR-131 > URL: http://jira.codehaus.org/browse/MWAR-131 > Project: Maven 2.x War Plugin > Issue Type: Improvement >Affects Versions: 2.1-alpha-1 >Reporter: Stephane Nicoll >Assignee: Stephane Nicoll > Fix For: 2.1-alpha-2 > > > If the server-side code of a war project need to be reused somewhere, we need > to deploy the content of the WEB-INF/classes to be able to use it as a > dependency -- 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: (MNG-3479) Maven Embedder incorrectly resolves properties in multiprojects and incorrectly resolves dependency management for POM dependencies
Maven Embedder incorrectly resolves properties in multiprojects and incorrectly resolves dependency management for POM dependencies --- Key: MNG-3479 URL: http://jira.codehaus.org/browse/MNG-3479 Project: Maven 2 Issue Type: Bug Components: Embedding Affects Versions: 2.0.8 Reporter: Ben Gidley Attachments: MultiprojectTestCase.patch Maven Embedder incorrectly resolves properties in multiprojects and incorrectly resolves dependency management for POM dependencies This was first noticed using IntelliJ embedder - see JIRA's are * http://www.jetbrains.net/jira/browse/IDEA-17318 - Parent POM properties are not working in child POM's * http://www.jetbrains.net/jira/browse/IDEA-17320 - Dependency Management section is not cascading correctly The first issue prevents maven embedder from parsing a child POM that uses a parent POM to set the version of an artifact, if the parent POM using properties to set the version. The second issue shows even if you set the version explicitly the parent POM's dependency management section does not cascade in embedder (but it does in maven) correctly for POM type dependencies. I have written a unit test (attached) to embedder to test for this. But am unsure how to fix. -- 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-3479) Maven Embedder incorrectly resolves properties in multiprojects and incorrectly resolves dependency management for POM dependencies
[ http://jira.codehaus.org/browse/MNG-3479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=128312#action_128312 ] Ben Gidley commented on MNG-3479: - Further experimentation has shown the properties issue only effect items whose type is NOT jar. > Maven Embedder incorrectly resolves properties in multiprojects and > incorrectly resolves dependency management for POM dependencies > --- > > Key: MNG-3479 > URL: http://jira.codehaus.org/browse/MNG-3479 > Project: Maven 2 > Issue Type: Bug > Components: Embedding >Affects Versions: 2.0.8 >Reporter: Ben Gidley > Attachments: MultiprojectTestCase.patch > > > Maven Embedder incorrectly resolves properties in multiprojects and > incorrectly resolves dependency management for POM dependencies > This was first noticed using IntelliJ embedder - see JIRA's are > * http://www.jetbrains.net/jira/browse/IDEA-17318 - Parent POM properties are > not working in child POM's > * http://www.jetbrains.net/jira/browse/IDEA-17320 - Dependency Management > section is not cascading correctly > The first issue prevents maven embedder from parsing a child POM that uses a > parent POM to set the version of an artifact, if the parent POM using > properties to set the version. > The second issue shows even if you set the version explicitly the parent > POM's dependency management section does not cascade in embedder (but it does > in maven) correctly for POM type dependencies. > I have written a unit test (attached) to embedder to test for this. But am > unsure how to fix. -- 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: (MSITE-292) Swedish translation for the site
[ http://jira.codehaus.org/browse/MSITE-292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg updated MSITE-292: -- Affects Version/s: 2.0-beta-6 Component/s: (was: internationalization) localization > Swedish translation for the site > > > Key: MSITE-292 > URL: http://jira.codehaus.org/browse/MSITE-292 > Project: Maven 2.x Site Plugin > Issue Type: Improvement > Components: localization >Affects Versions: 2.0-beta-6 >Reporter: Johan Andrén >Assignee: Dennis Lundberg >Priority: Minor > Attachments: project-info-report_sv_SE.properties, > site-plugin_sv_SE.properties > > > I have attached UTF-8 encoded translations of both the > project-info-report.properties and site-plugin.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: (MSITE-292) Swedish translation for the site
[ http://jira.codehaus.org/browse/MSITE-292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg closed MSITE-292. - Resolution: Fixed Fix Version/s: 2.0-beta-7 Patches applied with modifications and new SNAPSHOTs have been deployed. Tack så mycket! I also added a properties file for maven-doxia-tools. The files were converted to ISO-8859-1 before being committed, as per previous discussions. > Swedish translation for the site > > > Key: MSITE-292 > URL: http://jira.codehaus.org/browse/MSITE-292 > Project: Maven 2.x Site Plugin > Issue Type: Improvement > Components: localization >Affects Versions: 2.0-beta-6 >Reporter: Johan Andrén >Assignee: Dennis Lundberg >Priority: Minor > Fix For: 2.0-beta-7 > > Attachments: project-info-report_sv_SE.properties, > site-plugin_sv_SE.properties > > > I have attached UTF-8 encoded translations of both the > project-info-report.properties and site-plugin.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: (MSITE-249) Internationalization: Adapt generated directory layout to best practices
[ http://jira.codehaus.org/browse/MSITE-249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg closed MSITE-249. - Resolution: Won't Fix > Internationalization: Adapt generated directory layout to best practices > > > Key: MSITE-249 > URL: http://jira.codehaus.org/browse/MSITE-249 > Project: Maven 2.x Site Plugin > Issue Type: Improvement > Components: internationalization >Reporter: Alexander Hars > > The current directory layout is based on the assumption of a privileged > 'default' language. Localized content for this language is placed into the > root directory. All other language-specific content is placed into > locale-specific subdirectories. > However, in internationalization, current best practice is to place ALL > localized content into subdirectories named after the 2 digit locale > abbreviation. Even the default language. (This, of course, is how the Maven > structures its site source tree, too). > Having all localized content using the same structure has many advantages > (including that relative links are the same in all languages, it is easy to > switch from one language to the next, etc.). In addition, it cleanly > separates the localized content from the content that is necessary to inform > a user who arrives the first time and who is not automatically redirected to > the right language section that he needs to choose the language/preferred > country etc. > In the current layout, the site/index.html has both the task of serving the > welcome page content in the default language as well as helping users to make > a choice about their preferred language. In the clean structure where all > localized content is in subdirectories, the root index.html would only need > to help the user make the change between available languages, the index.html > in the subdirectories would serve as the localized welcome page. They can > easily be translated, there would be no special requirement for the default > language's welcome page. (of course all pages would have some menu for > switching languages, but it would not be prominent). > It would be quite simple to make this change. For backward compatibility, one > could add a property that preserves the old structure. > I know that the privileged default language approach by Maven was intended as > a feature. But it certainly is not a best practice and has significant > drawbacks. We should change it. > > -- 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-3479) Maven Embedder incorrectly resolves properties in multiprojects and incorrectly resolves dependency management for POM dependencies
[ http://jira.codehaus.org/browse/MNG-3479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=128328#action_128328 ] Milos Kleint commented on MNG-3479: --- which version of maven-embedder is IDEA using? I doubt it's 2.0.8, as the embedder code in 2.0.x branch is rather unusable. It's more likely a 2.1-SNAPSHOT of sorts. > Maven Embedder incorrectly resolves properties in multiprojects and > incorrectly resolves dependency management for POM dependencies > --- > > Key: MNG-3479 > URL: http://jira.codehaus.org/browse/MNG-3479 > Project: Maven 2 > Issue Type: Bug > Components: Embedding >Affects Versions: 2.0.8 >Reporter: Ben Gidley > Attachments: MultiprojectTestCase.patch > > > Maven Embedder incorrectly resolves properties in multiprojects and > incorrectly resolves dependency management for POM dependencies > This was first noticed using IntelliJ embedder - see JIRA's are > * http://www.jetbrains.net/jira/browse/IDEA-17318 - Parent POM properties are > not working in child POM's > * http://www.jetbrains.net/jira/browse/IDEA-17320 - Dependency Management > section is not cascading correctly > The first issue prevents maven embedder from parsing a child POM that uses a > parent POM to set the version of an artifact, if the parent POM using > properties to set the version. > The second issue shows even if you set the version explicitly the parent > POM's dependency management section does not cascade in embedder (but it does > in maven) correctly for POM type dependencies. > I have written a unit test (attached) to embedder to test for this. But am > unsure how to fix. -- 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: (MNG-3475) Some directories are not basedir aligned
[
http://jira.codehaus.org/browse/MNG-3475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann updated MNG-3475:
---
Attachment: base-directory-alignment.patch
Not even that {{DefaultPathTranslator}} misses some directories, it crashes on
certain inputs, too. E.g. {{alignToBaseDirectory( "${basedir}", basedir )}}
bails out with a {{StringIndexOutOfBoundsException}}.
I took this opportunity to clean this component up, adding javadocs and unit
tests.
> Some directories are not basedir aligned
>
>
> Key: MNG-3475
> URL: http://jira.codehaus.org/browse/MNG-3475
> Project: Maven 2
> Issue Type: Bug
> Components: POM
>Affects Versions: 2.0.8
>Reporter: Benjamin Bentmann
> Attachments: base-directory-alignment.patch,
> base-directory-alignment.patch
>
>
> The output from
> {code:xml}
> ${project.build.sourceDirectory}
> ${project.build.testSourceDirectory}
> ${project.build.scriptSourceDirectory}
> ${project.build.directory}
> ${project.build.outputDirectory}
> ${project.build.testOutputDirectory}
> ${project.reporting.outputDirectory}
> {code}
> delivers something like
> {noformat}
> [echo] M:\maven\z\antrun\src\main\java
> [echo] M:\maven\z\antrun\src\test\java
> [echo] src/main/scripts
> [echo] M:\maven\z\antrun\target
> [echo] M:\maven\z\antrun\target\classes
> [echo] M:\maven\z\antrun\target\test-classes
> [echo] target/site
> {noformat}
> revealing that neither the script source directory nor the reporting output
> directory are basedir aligned.
--
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: (MNG-3480) Extend unit test for DefaultMavenProjectBuilder to check inheritance from super POM
Extend unit test for DefaultMavenProjectBuilder to check inheritance from super POM --- Key: MNG-3480 URL: http://jira.codehaus.org/browse/MNG-3480 Project: Maven 2 Issue Type: Task Components: POM Reporter: Benjamin Bentmann Priority: Trivial Attachments: project-builder-minimal-pom-test.patch I originally wanted to create a unit test to trigger the failures Brian mentioned in MNG-3478. I ended up with a test that doesn't fail as expected but it might be useful nevertheless. -- 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-1974) Upload Saxon 9.0.0.2
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=128330#action_128330 ] Raymond Feng commented on MAVENUPLOAD-1974: --- The jars are extracted from orginal zip downloaded from http://superb-east.dl.sourceforge.net/sourceforge/saxon/saxonb9-0-0-2j.zip and they are not built by maven. I think it's probably better to leave the dependencies empty and have the modules that reference these artifacts to take care of the dependency declarations. > Upload Saxon 9.0.0.2 > > > Key: MAVENUPLOAD-1974 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1974 > Project: maven-upload-requests > Issue Type: Bug >Reporter: Luciano Resende > > The Tuscany project has a dependency on saxon 9.0.0.2 and needs it available > in a maven repo. > We have already contact the Saxon owner for authorization, and he said he is > OK, but won't do it. > > http://sourceforge.net/mailarchive/message.php?msg_id=46DAF629.8090908%40apache.org > Artifact information below > A temporary repository was created at : >http://people.apache.org/~rfeng/tuscany/maven/ > A archive is available at : >http://people.apache.org/~rfeng/tuscany/maven/saxon.tar.gz -- 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: (MSITE-251) tr locale support
[ http://jira.codehaus.org/browse/MSITE-251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg closed MSITE-251. - Assignee: Dennis Lundberg Resolution: Fixed Fix Version/s: 2.0-beta-7 > tr locale support > - > > Key: MSITE-251 > URL: http://jira.codehaus.org/browse/MSITE-251 > Project: Maven 2.x Site Plugin > Issue Type: New Feature > Components: localization > Environment: Windows XP >Reporter: gulcan yalcinkaya >Assignee: Dennis Lundberg >Priority: Trivial > Fix For: 2.0-beta-7 > > Attachments: project-info-report_tr.properties, > site-plugin_tr.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: (MSITE-212) Catalan Language
[ http://jira.codehaus.org/browse/MSITE-212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg closed MSITE-212. - Assignee: Dennis Lundberg Resolution: Fixed Fix Version/s: 2.0-beta-7 > Catalan Language > > > Key: MSITE-212 > URL: http://jira.codehaus.org/browse/MSITE-212 > Project: Maven 2.x Site Plugin > Issue Type: New Feature > Components: localization >Reporter: Javier de Ros >Assignee: Dennis Lundberg > Fix For: 2.0-beta-7 > > Attachments: site-plugin_ca.properties > > > That's the Catalan language properties for the maven site 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] Created: (MARTIFACT-11) Do not use FileReader/FileWriter
Do not use FileReader/FileWriter
Key: MARTIFACT-11
URL: http://jira.codehaus.org/browse/MARTIFACT-11
Project: Maven Artifact
Issue Type: Improvement
Affects Versions: 3.0-alpha-1
Reporter: Benjamin Bentmann
Priority: Trivial
Attachments: avoid-platform-specific-encoding.patch
Using {{FileReader}} or {{FileWriter}} makes code dependent on the platform's
default encoding. For platform-independent behavior, the tests should use a
fixed encoding.
--
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-1979) "net.sf.jtreemap","[EMAIL PROTECTED]:/home/groups/o/ob/objectlabkit/htdocs/m2-repo","rsync_ssh","Marcin Jekot","[EMAIL PROTECTED]",,
"net.sf.jtreemap","[EMAIL PROTECTED]:/home/groups/o/ob/objectlabkit/htdocs/m2-repo","rsync_ssh","Marcin Jekot","[EMAIL PROTECTED]",, - Key: MAVENUPLOAD-1979 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1979 Project: maven-upload-requests Issue Type: Task Reporter: Marcin Jekot -- 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-1965) Upload JMesa
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=128341#action_128341 ] Jeff Johnston commented on MAVENUPLOAD-1965: The xhtmlrenderer is just an optional run-time dependency though. It is used if someone wants to render a table in PDF form. Other than that the table is completely functional! > Upload JMesa > > > Key: MAVENUPLOAD-1965 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1965 > Project: maven-upload-requests > Issue Type: Wish >Reporter: Jeff Johnston > > I was hoping that you could upload JMesa to the Maven repositories. > This is where the project can be found. > http://code.google.com/p/jmesa > My user name of extremecomponents is all over the project, but here is the > official link: > http://code.google.com/u/extremecomponents/ > I appreciate your help! > -Jeff Johnston -- 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
