[jira] Commented: (MRELEASE-699) release:update-versions should support -DreleaseVersion too (not only -DdevelopmentVersion), so it also supports not suffixing the version with -SNAPSHOT
[ https://jira.codehaus.org/browse/MRELEASE-699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=277763#comment-277763 ] Brett Porter commented on MRELEASE-699: --- There's several things here: * I'm not quite sure of the motivation for update-versions in the first place - maybe we should recommend the versions plugin instead * regardless of the above, we need to document the differences, and fix the misleading statement (or apply this patch) * we still need to look at the one line change that appears to be correct but doesn't reference a specific fix > release:update-versions should support -DreleaseVersion too (not only > -DdevelopmentVersion), so it also supports not suffixing the version with > -SNAPSHOT > - > > Key: MRELEASE-699 > URL: https://jira.codehaus.org/browse/MRELEASE-699 > Project: Maven 2.x Release Plugin > Issue Type: Improvement >Reporter: Geoffrey De Smet > Attachments: > 0001-MRELEASE-699-release-update-versions-should-support-.patch > > > The documentation > > http://maven.apache.org/plugins/maven-release-plugin/examples/update-versions.html > states "The update-versions goal can use the same properties used by the > prepare goal for specifying the versions to be used." > That's not true, as releaseVersion is not supported: > > http://maven.apache.org/plugins/maven-release-plugin/prepare-mojo.html#releaseVersion > This means, that if you do this: > mvn --batch-mode release:update-versions -DdevelopmentVersion=1.2.0 > that the set version is not 1.2.0, but in fact 1.2.0-SNAPSHOT. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MRELEASE-699) release:update-versions should support -DreleaseVersion too (not only -DdevelopmentVersion), so it also supports not suffixing the version with -SNAPSHOT
[ https://jira.codehaus.org/browse/MRELEASE-699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=277764#comment-277764 ] Geoffrey De Smet commented on MRELEASE-699: --- There is an alternative plugin to change the versions: http://maven.apache.org/plugins/maven-release-plugin/update-versions-mojo.html The release plugin goal "update-versions" should probably be deprecated in favor of that plugin. http://maven.apache.org/plugins/maven-release-plugin/update-versions-mojo.html > release:update-versions should support -DreleaseVersion too (not only > -DdevelopmentVersion), so it also supports not suffixing the version with > -SNAPSHOT > - > > Key: MRELEASE-699 > URL: https://jira.codehaus.org/browse/MRELEASE-699 > Project: Maven 2.x Release Plugin > Issue Type: Improvement >Reporter: Geoffrey De Smet > Attachments: > 0001-MRELEASE-699-release-update-versions-should-support-.patch > > > The documentation > > http://maven.apache.org/plugins/maven-release-plugin/examples/update-versions.html > states "The update-versions goal can use the same properties used by the > prepare goal for specifying the versions to be used." > That's not true, as releaseVersion is not supported: > > http://maven.apache.org/plugins/maven-release-plugin/prepare-mojo.html#releaseVersion > This means, that if you do this: > mvn --batch-mode release:update-versions -DdevelopmentVersion=1.2.0 > that the set version is not 1.2.0, but in fact 1.2.0-SNAPSHOT. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (WAGON-346) LightWeight http wagon not thread-safe
[ https://jira.codehaus.org/browse/WAGON-346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nicolas de loof closed WAGON-346. - Resolution: Fixed Fix Version/s: 2.0 1.x Fixed in 1.x using a class level synchronized block > LightWeight http wagon not thread-safe > -- > > Key: WAGON-346 > URL: https://jira.codehaus.org/browse/WAGON-346 > Project: Maven Wagon > Issue Type: Bug > Components: wagon-http-lightweight >Affects Versions: 1.0 > Environment: maven 3 with Aether >Reporter: nicolas de loof > Fix For: 1.x, 2.0 > > > Aether (maven3) by default parallelized metadata resolution on 4 threads > (aether.metadataResolver.threads) and artifacts downloading on 5 > (maven.artifact.threads). > In such context, Wagon is not used sequentially. > LightWeightHttpWagon is designed for mono-thread, sequential usage. It rely > on system properties and on setting/resetting java.net.Authenticator > singleton. > The result is that, in some cases (typically : when settings defines many > repositories with various credentials), credentials may not apply and > download will fail > A potential fix is > - to use Java5 URL.openConnection(Proxy) instead of using system properties > - to use a shared, singleton java.net.Authenticator that lookup repositories > to match the requested URL -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (MPOM-28) apache jar resource bundle does not appear to be documented
apache jar resource bundle does not appear to be documented --- Key: MPOM-28 URL: https://issues.apache.org/jira/browse/MPOM-28 Project: Maven POMs Issue Type: Bug Components: asf Reporter: Sebb There does not appear to be any documentation for the apache resource bundle; in particular there is no link to JIRA or release notes. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (WAGON-346) LightWeight http wagon not thread-safe
[ https://jira.codehaus.org/browse/WAGON-346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=22#comment-22 ] Mark Struberg commented on WAGON-346: - Nicolas, I have not yet looked at the latest source in the 1.x trunk (I'm currently at work), but synchronizing on any wagon class will probably not work. If wagon is used via dependency, then each project will get it's own ClassLoader, thus you could only lock usages in the build, or even in the same mojo invocation (depends on the effective ClassLoader hierarchy). But the proxy is set via System.properties and a singleton_per_OS. > LightWeight http wagon not thread-safe > -- > > Key: WAGON-346 > URL: https://jira.codehaus.org/browse/WAGON-346 > Project: Maven Wagon > Issue Type: Bug > Components: wagon-http-lightweight >Affects Versions: 1.0 > Environment: maven 3 with Aether >Reporter: nicolas de loof > Fix For: 1.x, 2.0 > > > Aether (maven3) by default parallelized metadata resolution on 4 threads > (aether.metadataResolver.threads) and artifacts downloading on 5 > (maven.artifact.threads). > In such context, Wagon is not used sequentially. > LightWeightHttpWagon is designed for mono-thread, sequential usage. It rely > on system properties and on setting/resetting java.net.Authenticator > singleton. > The result is that, in some cases (typically : when settings defines many > repositories with various credentials), credentials may not apply and > download will fail > A potential fix is > - to use Java5 URL.openConnection(Proxy) instead of using system properties > - to use a shared, singleton java.net.Authenticator that lookup repositories > to match the requested URL -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (MPOM-29) apache jar resource bundle bugs
apache jar resource bundle bugs --- Key: MPOM-29 URL: https://issues.apache.org/jira/browse/MPOM-29 Project: Maven POMs Issue Type: Bug Components: asf Environment: version=1.4 groupId=org.apache artifactId=apache-jar-resource-bundle Reporter: Sebb 1) The included NOTICE.txt file contains 4 leading comment lines and a blank line which should not be there. 2) There are spurious blank lines in the NOTICE.vm template. The NOTICE file should not be bigger than necessary, so these ought to be removed. 3) There is a spurious blank line at the start of the LICENSE.vm template. Patch to follow for 2 and 3. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (MPOM-29) apache jar resource bundle bugs
[ https://issues.apache.org/jira/browse/MPOM-29?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebb updated MPOM-29: - Attachment: MPOM-29.patch Patch for apache-jar-resource-bundle and apache-jar-txt-resource-bundle > apache jar resource bundle bugs > --- > > Key: MPOM-29 > URL: https://issues.apache.org/jira/browse/MPOM-29 > Project: Maven POMs > Issue Type: Bug > Components: asf > Environment: version=1.4 > groupId=org.apache > artifactId=apache-jar-resource-bundle >Reporter: Sebb > Attachments: MPOM-29.patch > > > 1) The included NOTICE.txt file contains 4 leading comment lines and a blank > line which should not be there. > 2) There are spurious blank lines in the NOTICE.vm template. The NOTICE file > should not be bigger than necessary, so these ought to be removed. > 3) There is a spurious blank line at the start of the LICENSE.vm template. > Patch to follow for 2 and 3. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-1977) Global dependency exclusions
[ https://jira.codehaus.org/browse/MNG-1977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=277793#comment-277793 ] Jean-Noel Rouvignac commented on MNG-1977: -- @Arnaud Sorry, I went for the easiest to implement. If you do not like it this way, fair enough, we can do it otherwise. I originally started with such change to the pom.xml: com.mycompany myproject optional ... ... ... No I did not test with older versions of maven. I saw that maven-3 has got some validation mechanism for the scope so I think it would reject it. For maven-2 I need to check. Indeed the following scenario would be catastrophic: "And when a maven version ignores it, what does it do ? It uses the compile scope ? #fail in that case, instead of excluding it, you explicitely add it (transitively)". I will test both of these and let you know. Same, it does not really matter to me which mechanism you prefer to use. Just tell me how you want it to look in the pom.xml and I can have a look at doing it. Jean-Noel > Global dependency exclusions > > > Key: MNG-1977 > URL: https://jira.codehaus.org/browse/MNG-1977 > Project: Maven 2 & 3 > Issue Type: New Feature > Components: POM >Reporter: Kees de Kooter > Fix For: 3.1 > > Attachments: global_excls_it-test_v2.patch, > global_excls_maven3_v2.patch > > > I depend on some libraries, which in turn depend on something > (which in turn depend on something) that I don't want, because I declare > some other artifact in my pom.xml. > A concrete example: I don't want that the artifact "xerces" is imported in > my project because I declare to depend on "xercesImpl" which ships newer > libraries but with the same namespaces. > I guess I would need an "exclude transitive dependency at all", either > globally or from this and that artifact. I saw the tag, but it > forces me to be very verbose and have exact control on what is required by a > dependency. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SCM-612) maven-release-plugin causes mercurial scm provider to fail when only a module is released
[
https://jira.codehaus.org/browse/SCM-612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=277803#comment-277803
]
Andreas Ebbert-Karroum commented on SCM-612:
Hi,
I haven't tried it, but I doubt that this change is fixing everything that I
described on the mailing list.
{quote}
h2. Step 1
So, I started with a very simple multi-module project (/pom.xml and
/multi/pom.xml) and tried to release just a single module (multi). It turned
out that this is not possible, because during the release:perform phase, the
whole hg repository is checked out, and the build is started in the root of
that repository.
=> Use the latest maven-release-plugin:2.2-SNAPSHOT in which
MRELEASE-457is fixed.
h2. Step 2
The new dependencies with the snapshot release plugin also updates to a
newer hg scm provider. The new hg scm provider has the interesting new habit
to throw an exception, when you want to tag something, which does not
concern the whole repository.
Caused by: org.apache.maven.scm.ScmException: This provider doesn't support
tagging subsets of a directory
at
org.apache.maven.scm.provider.hg.command.tag.HgTagCommand.executeTagCommand(HgTagCommand.java:77)
at
org.apache.maven.scm.command.tag.AbstractTagCommand.executeCommand(AbstractTagCommand.java:81)
at
org.apache.maven.scm.command.AbstractCommand.execute(AbstractCommand.java:59)
... 29 more
=> Update the dependencies of maven-release-plugin:2.2-SNAPSHOT to use
maven-scm-provider-hg:1.4
h2. Step 3
The next step was to move the parent pom out of the root of the hg
repository. We have a standardized layout in our hg repositories (to take
into account various tradeoffs between maven, m2eclipse, hudson, etc.) that
we have all projects in directories under the root directory. So I tried to
have
/ root / pom.xml (having a module ../multi)
and
/ multi / pom.xml (having a parent ../root)
The release plugin did not like that at all:
[INFO] EXECUTING: cmd.exe /X /C "hg commit --message "[maven-release-plugin]
prepare release root-1.6" C:\Temp\releasetest\parent\pom.xml
C:\Temp\releasetest\multi\pom.xml"
[INFO] EXECUTING: cmd.exe /X /C "*hg push file:///C:/Temp/releasetestrepo*"
[INFO] Tagging release with the label root-1.6...
[INFO] EXECUTING: cmd.exe /X /C "hg tag --message "[maven-release-plugin]
copy for tag root-1.6" root-1.6"
[INFO] EXECUTING: cmd.exe /X /C "*hg push file:///C:/Temp*"
[ERROR]
EXECUTION FAILED
Execution of cmd : push failed with exit code: -1.
Working directory was:
c:\temp\releasetest
Your Hg installation seems to be valid and complete.
Hg version: 1.6.2 (OK)
This is probably a bug, but I have no idea if this is in the scm provider,
release plugin, shared components, ... I'm glad to create a jira issue for
it, but would like to do so for the right project.
=> Having no pom.xml in the root of the repository is apparently a bad idea.
But we need to have our "parent" in a folder under the root directly. So I
created a thin dummy pom, which just has the real parent as module.
h2. Step 4
So we now have:
/ pom.xml
/ parent / pom.xml
/ multi / pom.xml
While I created the root pom.xml, I tried to optimize a bit and included
localCheckout=true to the plugin configuration, so that the tag checkout
does not happen from the remote repository, but from the local one. Bad
idea:
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-release-plugin:2.2-SNAPSHOT:perform
(default-cli) on project root: The scm url is invalid.
[ERROR] - An hg 'file' url must be on the form 'file:///' or
'file://localhost/'.
My scm url is: scm:hg:file:///C:/Temp/releasetestrepo
So also the "remote" hg repository is on the local filesystem, but when the
local checkout occurs, the url is apparently not constructed correctly.
=> Ok, no localCheckout. Not a big deal, moving on.
h2. Step 5
If possible, I don't want the /parent/pom.xml to inherit from /pom.xml,
because it may well be, that it needs to inherit from something completely
different. I only wanted to use the /pom.xml as a forwarder to
/parent/pom.xml. So I tried that, and tried to release the "multi"-module. I
did this by running from working directory /parent the command "mvn
--batch-mode -pl multi release:prepare". But I could not find a working scm
configuration in /parent/pom.xml
When it was set to "scm:hg:file:///C:/Temp/releasetestrepo/parent" I got
this error - apperently it tried to replace the current module name "parent"
in the scm url with "multi":
[INFO] EXECUTING: cmd.exe /X /C "hg commit --message "[maven-release-plugin]
prepare release multi-1.22" C:\Temp\releasetest\multi\pom.xml"
[INFO] EXECUTING: cmd.exe /X /C "hg push *
file:///C:/Temp/releasetestrepo/multi*"
But when I set the scm url to the correct value
"scm:hg:file:
[jira] Closed: (MRRESOURCES-57) Incorrect documentation of outputDirectory?
[
https://jira.codehaus.org/browse/MRRESOURCES-57?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Scholte closed MRRESOURCES-57.
-
Resolution: Fixed
Fix Version/s: 1.3
Assignee: Robert Scholte
Fixed in [rev. 1165423|http://svn.apache.org/viewvc?rev=1165423&view=rev]
There were even more fields which used {{expression}} instead of
{{default-value}}. Fixed those as well.
> Incorrect documentation of outputDirectory?
> ---
>
> Key: MRRESOURCES-57
> URL: https://jira.codehaus.org/browse/MRRESOURCES-57
> Project: Maven 2.x Remote Resources Plugin
> Issue Type: Bug
>Affects Versions: 1.2.1
> Environment:
> http://maven.apache.org/plugins/maven-remote-resources-plugin/process-mojo.html#outputDirectory
>Reporter: sebbaz+ch
>Assignee: Robert Scholte
> Fix For: 1.3
>
>
> The description for outputDirectory says:
> The directory where processed resources will be placed for packaging.
> Type: java.io.File
> Required: No
> Expression: ${project.build.directory}/maven-shared-archive-resources
> However, that does not look correct - surely an expression should be a plain
> variable reference, and not include trailing constant text?
> The Expression looks more like the Default.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (DOXIATOOLS-11) add Doxia Eclipse Editor to Apache CI server
[
https://jira.codehaus.org/browse/DOXIATOOLS-11?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=277825#comment-277825
]
Herve Boutemy commented on DOXIATOOLS-11:
-
tried it, but it fails too
I can't build the tool, neither on my machine nor on CI server
actual build process:
{noformat}mvn clean install -f
doxia-osgi/org.apache.maven.doxia.eclipse.dependencies/pom.xml
mvn clean install -f doxia-osgi/pom.xml
mvn clean install -f eclipse-plugins/pom.xml{noformat}
but no luck
what are the command lines to launch to build Doxia Eclipse Editor?
what stupid mistake am I doing?
> add Doxia Eclipse Editor to Apache CI server
>
>
> Key: DOXIATOOLS-11
> URL: https://jira.codehaus.org/browse/DOXIATOOLS-11
> Project: Maven Doxia Tools
> Issue Type: New Feature
> Components: Doxia Eclipse Editor
>Reporter: Herve Boutemy
>
> latest builds should be downloadable from
> https://builds.apache.org//view/M-R/view/Maven/
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (MPOM-28) apache jar resource bundle does not appear to be documented
[ https://issues.apache.org/jira/browse/MPOM-28?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hervé Boutemy updated MPOM-28: -- Component/s: (was: asf) apache-jar-resource-bundle Affects Version/s: APACHE-JAR-RESOURCE-BUNDLE-1.4 > apache jar resource bundle does not appear to be documented > --- > > Key: MPOM-28 > URL: https://issues.apache.org/jira/browse/MPOM-28 > Project: Maven POMs > Issue Type: Bug > Components: apache-jar-resource-bundle >Affects Versions: APACHE-JAR-RESOURCE-BUNDLE-1.4 >Reporter: Sebb > > There does not appear to be any documentation for the apache resource bundle; > in particular there is no link to JIRA or release notes. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (MPOM-30) It should be possible to use something other than "project.name" for the header
It should be possible to use something other than "project.name" for the header --- Key: MPOM-30 URL: https://issues.apache.org/jira/browse/MPOM-30 Project: Maven POMs Issue Type: Improvement Components: apache-jar-resource-bundle Reporter: Hervé Boutemy http://jira.codehaus.org/browse/MRRESOURCES-12 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (MPOM-30) It should be possible to use something other than "project.name" for the header
[ https://issues.apache.org/jira/browse/MPOM-30?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hervé Boutemy closed MPOM-30. - Resolution: Fixed fixed in [r508182|http://svn.apache.org/viewvc?view=revision&revision=508182] in sandbox merged to trunk in [r512287|http://svn.apache.org/viewvc?view=revision&revision=512287] > It should be possible to use something other than "project.name" for the > header > --- > > Key: MPOM-30 > URL: https://issues.apache.org/jira/browse/MPOM-30 > Project: Maven POMs > Issue Type: Improvement > Components: apache-jar-resource-bundle >Reporter: Hervé Boutemy > > http://jira.codehaus.org/browse/MRRESOURCES-12 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Reopened] (MPOM-30) It should be possible to use something other than "project.name" for the header
[ https://issues.apache.org/jira/browse/MPOM-30?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hervé Boutemy reopened MPOM-30: --- > It should be possible to use something other than "project.name" for the > header > --- > > Key: MPOM-30 > URL: https://issues.apache.org/jira/browse/MPOM-30 > Project: Maven POMs > Issue Type: Improvement > Components: apache-jar-resource-bundle >Reporter: Hervé Boutemy > > http://jira.codehaus.org/browse/MRRESOURCES-12 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (MPOM-30) It should be possible to use something other than "project.name" for the header
[ https://issues.apache.org/jira/browse/MPOM-30?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hervé Boutemy closed MPOM-30. - Resolution: Fixed > It should be possible to use something other than "project.name" for the > header > --- > > Key: MPOM-30 > URL: https://issues.apache.org/jira/browse/MPOM-30 > Project: Maven POMs > Issue Type: Improvement > Components: apache-jar-resource-bundle >Reporter: Hervé Boutemy > > http://jira.codehaus.org/browse/MRRESOURCES-12 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MRRESOURCES-12) It should be possible to use something other than "project.name" for the header
[
https://jira.codehaus.org/browse/MRRESOURCES-12?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=277826#comment-277826
]
Herve Boutemy commented on MRRESOURCES-12:
--
https://issues.apache.org/jira/browse/MPOM-30
> It should be possible to use something other than "project.name" for the
> header
>
>
> Key: MRRESOURCES-12
> URL: https://jira.codehaus.org/browse/MRRESOURCES-12
> Project: Maven 2.x Remote Resources Plugin
> Issue Type: Improvement
>Affects Versions: 1.0-alpha-1, 1.0-alpha-2
>Reporter: Daniel Kulp
>Assignee: Daniel Kulp
> Fix For: 1.0-alpha-3
>
>
> "Adam Lally" :
> However, is there a way to override the name of
> the project that is written to the NOTICES and DISCLAIMER files?
> Currently each jar file uses its own artifact name (e.g. "Apache UIMA
> Java Framework Core") when really we want just the name of our project
> ("Apache UIMA").
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (MPOM-31) would be nice to optionally have license information in the NOTICE
would be nice to optionally have license information in the NOTICE -- Key: MPOM-31 URL: https://issues.apache.org/jira/browse/MPOM-31 Project: Maven POMs Issue Type: Improvement Components: apache-jar-resource-bundle Reporter: Hervé Boutemy http://jira.codehaus.org/browse/MRRESOURCES-9 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (MPOM-31) would be nice to optionally have license information in the NOTICE
[ https://issues.apache.org/jira/browse/MPOM-31?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hervé Boutemy closed MPOM-31. - Resolution: Fixed done in r506511 http://svn.apache.org/viewvc?view=revision&revision=506511 in sandbox merged to trunk in r512287 http://svn.apache.org/viewvc?view=revision&revision=512287 > would be nice to optionally have license information in the NOTICE > -- > > Key: MPOM-31 > URL: https://issues.apache.org/jira/browse/MPOM-31 > Project: Maven POMs > Issue Type: Improvement > Components: apache-jar-resource-bundle >Reporter: Hervé Boutemy > > http://jira.codehaus.org/browse/MRRESOURCES-9 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MRRESOURCES-9) For apache-jar-resource-bundle, would be nice to optionally have license information in the NOTICE
[ https://jira.codehaus.org/browse/MRRESOURCES-9?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=277827#comment-277827 ] Herve Boutemy commented on MRRESOURCES-9: - https://issues.apache.org/jira/browse/MPOM-31 > For apache-jar-resource-bundle, would be nice to optionally have license > information in the NOTICE > -- > > Key: MRRESOURCES-9 > URL: https://jira.codehaus.org/browse/MRRESOURCES-9 > Project: Maven 2.x Remote Resources Plugin > Issue Type: New Feature >Affects Versions: 1.0-alpha-1 >Reporter: Daniel Kulp >Assignee: Daniel Kulp > Fix For: 1.0-alpha-2 > > > The velocity template could be updated to optionally allow a "License" line > for each dependent project. Kind of like: > This product includes/uses software, Apache CXF Runtime Simple Frontend > (http://cwiki.apache.org/confluence/display/CXF/Index), > developed by Apache Software Foundation (http://www.apache.org/) > License: The Apache Software License, Version 2.0 > (http://www.apache.org/licenses/LICENSE-2.0.txt) > Would make auditing the NOTICE file a bit easier. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MPOM-28) apache jar resource bundle does not appear to be documented
[ https://issues.apache.org/jira/browse/MPOM-28?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13097640#comment-13097640 ] Hervé Boutemy commented on MPOM-28: --- added apache-jar-resource-bundle and versions 1.4 (released) + 1.5 (yet to be released) added jira issues MPOM-30 an MPOM-31 pointing to their respective MRRESSOURCE original issues there are other apache-* resources in svn: http://svn.apache.org/viewvc/maven/resources/trunk/ any idea on the place where we should document each one? > apache jar resource bundle does not appear to be documented > --- > > Key: MPOM-28 > URL: https://issues.apache.org/jira/browse/MPOM-28 > Project: Maven POMs > Issue Type: Bug > Components: apache-jar-resource-bundle >Affects Versions: APACHE-JAR-RESOURCE-BUNDLE-1.4 >Reporter: Sebb > > There does not appear to be any documentation for the apache resource bundle; > in particular there is no link to JIRA or release notes. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (ARCHETYPE-62) Allow package.html files to be included in an archetype
[
https://jira.codehaus.org/browse/ARCHETYPE-62?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Herve Boutemy updated ARCHETYPE-62:
---
Description:
A Java source folder may contain non Java resources such as JavaDoc
package.html etc.
{code:xml}
src/main/java/App.java
src/main/java/package.html
src/test/java/AppTest.java
src/main/java/package.html
{code}
Currently when specifying non Java resources they don't get distributed in the
packaged archetype jar.
was:
A Java source folder may contain non Java resources such as JavaDoc
package.html etc.
src/main/java/App.java
src/main/java/package.html
src/test/java/AppTest.java
src/main/java/package.html
Currently when specifying non Java resources they don't get distributed in the
packaged archetype jar.
> Allow package.html files to be included in an archetype
> ---
>
> Key: ARCHETYPE-62
> URL: https://jira.codehaus.org/browse/ARCHETYPE-62
> Project: Maven Archetype
> Issue Type: Improvement
>Affects Versions: 1.0-alpha-4
>Reporter: Martin Ahrer
> Fix For: 2.0-alpha-1
>
>
> A Java source folder may contain non Java resources such as JavaDoc
> package.html etc.
> {code:xml}
> src/main/java/App.java
> src/main/java/package.html
>
>
> src/test/java/AppTest.java
> src/main/java/package.html
> {code}
> Currently when specifying non Java resources they don't get distributed in
> the packaged archetype jar.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (DOXIATOOLS-11) add Doxia Eclipse Editor to Apache CI server
[ https://jira.codehaus.org/browse/DOXIATOOLS-11?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benson Margulies updated DOXIATOOLS-11: --- Attachment: typescript Captured results of my building. > add Doxia Eclipse Editor to Apache CI server > > > Key: DOXIATOOLS-11 > URL: https://jira.codehaus.org/browse/DOXIATOOLS-11 > Project: Maven Doxia Tools > Issue Type: New Feature > Components: Doxia Eclipse Editor >Reporter: Herve Boutemy > Attachments: typescript > > > latest builds should be downloadable from > https://builds.apache.org//view/M-R/view/Maven/ -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (DOXIATOOLS-11) add Doxia Eclipse Editor to Apache CI server
[ https://jira.codehaus.org/browse/DOXIATOOLS-11?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=277828#comment-277828 ] Benson Margulies commented on DOXIATOOLS-11: See attached? > add Doxia Eclipse Editor to Apache CI server > > > Key: DOXIATOOLS-11 > URL: https://jira.codehaus.org/browse/DOXIATOOLS-11 > Project: Maven Doxia Tools > Issue Type: New Feature > Components: Doxia Eclipse Editor >Reporter: Herve Boutemy > Attachments: typescript > > > latest builds should be downloadable from > https://builds.apache.org//view/M-R/view/Maven/ -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (DOXIATOOLS-11) add Doxia Eclipse Editor to Apache CI server
[ https://jira.codehaus.org/browse/DOXIATOOLS-11?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=277830#comment-277830 ] Vincent Siveton commented on DOXIATOOLS-11: --- You need to build doxia-osgi firstly and plugins secondly > add Doxia Eclipse Editor to Apache CI server > > > Key: DOXIATOOLS-11 > URL: https://jira.codehaus.org/browse/DOXIATOOLS-11 > Project: Maven Doxia Tools > Issue Type: New Feature > Components: Doxia Eclipse Editor >Reporter: Herve Boutemy > Attachments: typescript > > > latest builds should be downloadable from > https://builds.apache.org//view/M-R/view/Maven/ -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (SUREFIRE-766) Regression in excludes feature between surefire 2.6 and 2.7.
Regression in excludes feature between surefire 2.6 and 2.7.
Key: SUREFIRE-766
URL: https://jira.codehaus.org/browse/SUREFIRE-766
Project: Maven Surefire
Issue Type: Bug
Components: Junit 4.x support
Affects Versions: 2.9, 2.8.1, 2.8, 2.7.2, 2.7.1, 2.7
Reporter: Jonathan Hsieh
I have a build that excludes certain JUnit 4 test cases by allowing users to
specify a -Dtest.exclude.pattern=**/TestA*.java,**/TestB*.java style command
line argument. This worked for surefire 2.5, 2.6 but fails to work in 2.7,
2.7.1, 2.7.2, 2.8, 2.8.1, and 2.9 releases.
Here's how I pass in the excludes from the command line:
{code}
...
org.apache.maven.plugins
maven-surefire-plugin
always
**/Test*.java
**/*$*
${test.exclude.pattern}
...
{code}
and
{code}
...
...
**/${test.exclude}.java
...
{code}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SUREFIRE-766) Regression in excludes feature between surefire 2.6 and 2.7.
[
https://jira.codehaus.org/browse/SUREFIRE-766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=277831#comment-277831
]
Jonathan Hsieh commented on SUREFIRE-766:
-
Notice that I exclude **/Test*.java, yet TestFlumeShell runs.
{code}
Version 2.8.1 based build.
jon@grimlock:~/proj/cdh-flume$ mvn test
-Dtest.exclude.pattern="**/TestA*.java,**/TestF*.java"
...
---
T E S T S
---
Running dk.brics.automaton.TestAutomaton
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.089 sec
Running com.cloudera.flume.shell.TestFlumeShell
...
{code}
Notice that initially we start testing with TestConsistentHash
{code}
Version 2.6 based build.
jon@grimlock:~/proj/cdh-flume$ mvn test
...
---
T E S T S
---
Running com.cloudera.util.consistenthash.TestConsistentHash
Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.288 sec
Running com.cloudera.flume.master.TestMasterReport
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.487 sec
Running com.cloudera.flume.agent.diskfailover.TestConcurrentDFOMan
Tests run: 11, Failures: 0, Errors: 0, Skipped: 3, Time elapsed: 17.853 sec
Running com.cloudera.util.TestNetUtils
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.959 sec
Running com.cloudera.flume.agent.TestEndToEndAckFailureRecovery
^CDestroying 1 processes
Destroying process..
Destroyed 1 processes
{code}
Now we exclue TestC* and TestM* -- we have excluded thos tests and started with
TestEndToEndAckFailureRecovery.
{code}
jon@grimlock:~/proj/cdh-flume$ mvn test
-Dtest.exclude.pattern=**/TestC*.java,**/TestM*.java
...
Running com.cloudera.util.TestNetUtils
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 3.65 sec
Running com.cloudera.flume.agent.TestEndToEndAckFailureRecovery
^CDestroying 1 processes
{code}
> Regression in excludes feature between surefire 2.6 and 2.7.
>
>
> Key: SUREFIRE-766
> URL: https://jira.codehaus.org/browse/SUREFIRE-766
> Project: Maven Surefire
> Issue Type: Bug
> Components: Junit 4.x support
>Affects Versions: 2.7, 2.7.1, 2.7.2, 2.8, 2.8.1, 2.9
>Reporter: Jonathan Hsieh
>
> I have a build that excludes certain JUnit 4 test cases by allowing users to
> specify a -Dtest.exclude.pattern=**/TestA*.java,**/TestB*.java style command
> line argument. This worked for surefire 2.5, 2.6 but fails to work in 2.7,
> 2.7.1, 2.7.2, 2.8, 2.8.1, and 2.9 releases.
> Here's how I pass in the excludes from the command line:
> {code}
> ...
>
> org.apache.maven.plugins
> maven-surefire-plugin
>
> always
>
> **/Test*.java
>
>
> **/*$*
> ${test.exclude.pattern}
>
> ...
> {code}
> and
> {code}
> ...
>
>...
>
>
> **/${test.exclude}.java
>
> ...
> {code}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (DOXIATOOLS-11) add Doxia Eclipse Editor to Apache CI server
[
https://jira.codehaus.org/browse/DOXIATOOLS-11?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Herve Boutemy updated DOXIATOOLS-11:
Attachment: doxia-osgi.log
ok, we clearly don't have same source for doxia-osgi
I have latest from svn
{noformat}$ svn info
Chemin : .
URLÂ :
https://svn.apache.org/repos/asf/maven/sandbox/trunk/doxia/doxia-ide/eclipse/doxia-osgi
Racine du dépôt : https://svn.apache.org/repos/asf
UUID du dépôt : 13f79535-47bb-0310-9956-ffa450edef68
Révision : 1165458
Type de nÅud : répertoire
Tâche programmée : normale
Auteur de la dernière modification : hboutemy
Révision de la dernière modification : 1164874
Date de la dernière modification: 2011-09-03 17:35:48 +0200 (sam. 03 sept.
2011)
herve@bigmax:~/projets/maven/trunks/sandbox/doxia/doxia-ide/eclipse/doxia-osgi$
svn diff
herve@bigmax:~/projets/maven/trunks/sandbox/doxia/doxia-ide/eclipse/doxia-osgi${noformat}
it build multiple modules (added in
[r1164849|http://svn.apache.org/viewvc?diff_format=h&view=revision&revision=1164849])
I removed org/apache/maven/doxia/ide from my local repository and it complains
even more than ever :(
> add Doxia Eclipse Editor to Apache CI server
>
>
> Key: DOXIATOOLS-11
> URL: https://jira.codehaus.org/browse/DOXIATOOLS-11
> Project: Maven Doxia Tools
> Issue Type: New Feature
> Components: Doxia Eclipse Editor
>Reporter: Herve Boutemy
> Attachments: doxia-osgi.log, typescript
>
>
> latest builds should be downloadable from
> https://builds.apache.org//view/M-R/view/Maven/
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (DOXIATOOLS-11) add Doxia Eclipse Editor to Apache CI server
[ https://jira.codehaus.org/browse/DOXIATOOLS-11?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=277834#comment-277834 ] Benson Margulies commented on DOXIATOOLS-11: Indeed, when I do an 'up', it stops building. Hmm. > add Doxia Eclipse Editor to Apache CI server > > > Key: DOXIATOOLS-11 > URL: https://jira.codehaus.org/browse/DOXIATOOLS-11 > Project: Maven Doxia Tools > Issue Type: New Feature > Components: Doxia Eclipse Editor >Reporter: Herve Boutemy > Attachments: doxia-osgi.log, typescript > > > latest builds should be downloadable from > https://builds.apache.org//view/M-R/view/Maven/ -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (DOXIATOOLS-11) add Doxia Eclipse Editor to Apache CI server
[ https://jira.codehaus.org/browse/DOXIATOOLS-11?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=277833#comment-277833 ] Benson Margulies commented on DOXIATOOLS-11: /Users/benson/asf/mvn/doxia-sandbox/doxia-ide/eclipse/doxia-osgi svn info Path: . URL: https://svn.apache.org/repos/asf/maven/sandbox/trunk/doxia/doxia-ide/eclipse/doxia-osgi Repository Root: https://svn.apache.org/repos/asf Repository UUID: 13f79535-47bb-0310-9956-ffa450edef68 Revision: 1163340 Node Kind: directory Schedule: normal Last Changed Author: bimargulies Last Changed Rev: 1163339 Last Changed Date: 2011-08-30 15:10:41 -0400 (Tue, 30 Aug 2011) > add Doxia Eclipse Editor to Apache CI server > > > Key: DOXIATOOLS-11 > URL: https://jira.codehaus.org/browse/DOXIATOOLS-11 > Project: Maven Doxia Tools > Issue Type: New Feature > Components: Doxia Eclipse Editor >Reporter: Herve Boutemy > Attachments: doxia-osgi.log, typescript > > > latest builds should be downloadable from > https://builds.apache.org//view/M-R/view/Maven/ -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (DOXIATOOLS-11) add Doxia Eclipse Editor to Apache CI server
[ https://jira.codehaus.org/browse/DOXIATOOLS-11?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=277835#comment-277835 ] Benson Margulies commented on DOXIATOOLS-11: Vincent, it looks like trouble started with r1164849. Do you want to try to figure out what's amiss first? I can certainly debug this if needed. > add Doxia Eclipse Editor to Apache CI server > > > Key: DOXIATOOLS-11 > URL: https://jira.codehaus.org/browse/DOXIATOOLS-11 > Project: Maven Doxia Tools > Issue Type: New Feature > Components: Doxia Eclipse Editor >Reporter: Herve Boutemy > Attachments: doxia-osgi.log, typescript > > > latest builds should be downloadable from > https://builds.apache.org//view/M-R/view/Maven/ -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (DOXIATOOLS-11) add Doxia Eclipse Editor to Apache CI server
[ https://jira.codehaus.org/browse/DOXIATOOLS-11?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=277836#comment-277836 ] Benson Margulies commented on DOXIATOOLS-11: Note that the whole business of making a p2 repo containing doxia-osgi is not needed, it was an attempt at a solution to a problem I eventually fixed otherwise. > add Doxia Eclipse Editor to Apache CI server > > > Key: DOXIATOOLS-11 > URL: https://jira.codehaus.org/browse/DOXIATOOLS-11 > Project: Maven Doxia Tools > Issue Type: New Feature > Components: Doxia Eclipse Editor >Reporter: Herve Boutemy > Attachments: doxia-osgi.log, typescript > > > latest builds should be downloadable from > https://builds.apache.org//view/M-R/view/Maven/ -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (DOXIATOOLS-11) add Doxia Eclipse Editor to Apache CI server
[
https://jira.codehaus.org/browse/DOXIATOOLS-11?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=277837#comment-277837
]
Herve Boutemy commented on DOXIATOOLS-11:
-
I now understand the error we're facing:
{noformat}[INFO] Copying 15 resources to /
[DEBUG] file Monospaced.gif has a non filtered file extension
[DEBUG] copy
/home/herve/projets/maven/trunks/sandbox/doxia/doxia-ide/eclipse/eclipse/eclipse-plugins/plugins/org.apache.maven.doxia.ide.eclipse.common.ui/icons/dtool16/Monospaced.gif
to /icons/dtool16/Monospaced.gif
[INFO]
[INFO] BUILD FAILURE
[INFO]
{noformat}
see
http://svn.apache.org/viewvc/maven/sandbox/trunk/doxia/doxia-ide/eclipse/eclipse-plugins/plugins/org.apache.maven.doxia.ide.eclipse.common.ui/pom.xml?r1=1162759&r2=1163052&diff_format=h
{code:xml}
/
false
${basedir}
icons/**
{code}
we can't have targetPath=/, I can't write on /
I removed this configuration, and now it builds: seems like some temporary
build files (lib/ and icons/ directories) have been imported in svn, which
should not
we'll need to clean-up sometime
question: now that everything is built, how do I get an update site (to import
into Eclipse)?
> add Doxia Eclipse Editor to Apache CI server
>
>
> Key: DOXIATOOLS-11
> URL: https://jira.codehaus.org/browse/DOXIATOOLS-11
> Project: Maven Doxia Tools
> Issue Type: New Feature
> Components: Doxia Eclipse Editor
>Reporter: Herve Boutemy
> Attachments: doxia-osgi.log, typescript
>
>
> latest builds should be downloadable from
> https://builds.apache.org//view/M-R/view/Maven/
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (DOXIATOOLS-11) add Doxia Eclipse Editor to Apache CI server
[
https://jira.codehaus.org/browse/DOXIATOOLS-11?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=277838#comment-277838
]
Benson Margulies commented on DOXIATOOLS-11:
They aren't temp files.
The requirement here is that the icons live in ${basedir}/icons for the PDE,
and still end up in the JAR file at the root of the jar file. That / was
supposed to be relative to the root of the jar file! Maybe
${project.build.directory}?
The update site is in
doxia-ide/eclipse/eclipse-plugins/features/org.apache.maven.doxia.ide.eclipse.feature/target/site
when the build is complete.
For reasons involving bugs / missing features in tycho, it's much easier to
just build it there than in a separate directory.
> add Doxia Eclipse Editor to Apache CI server
>
>
> Key: DOXIATOOLS-11
> URL: https://jira.codehaus.org/browse/DOXIATOOLS-11
> Project: Maven Doxia Tools
> Issue Type: New Feature
> Components: Doxia Eclipse Editor
>Reporter: Herve Boutemy
> Attachments: doxia-osgi.log, typescript
>
>
> latest builds should be downloadable from
> https://builds.apache.org//view/M-R/view/Maven/
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Issue Comment Edited: (DOXIATOOLS-11) add Doxia Eclipse Editor to Apache CI server
[
https://jira.codehaus.org/browse/DOXIATOOLS-11?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=277838#comment-277838
]
Benson Margulies edited comment on DOXIATOOLS-11 at 9/5/11 8:27 PM:
They aren't temp files.
The requirement here is that the icons live in ${basedir}/icons for the PDE,
and still end up in the JAR file at the root of the jar file. That / was
supposed to be relative to the root of the jar file! Maybe
${project.build.directory}/target/classes? I wonder why it worked for me? I
don't have any icons cluttering up my root.
The update site is in
doxia-ide/eclipse/eclipse-plugins/features/org.apache.maven.doxia.ide.eclipse.feature/target/site
when the build is complete.
For reasons involving bugs / missing features in tycho, it's much easier to
just build it there than in a separate directory.
was (Author: bmargulies):
They aren't temp files.
The requirement here is that the icons live in ${basedir}/icons for the PDE,
and still end up in the JAR file at the root of the jar file. That / was
supposed to be relative to the root of the jar file! Maybe
${project.build.directory}?
The update site is in
doxia-ide/eclipse/eclipse-plugins/features/org.apache.maven.doxia.ide.eclipse.feature/target/site
when the build is complete.
For reasons involving bugs / missing features in tycho, it's much easier to
just build it there than in a separate directory.
> add Doxia Eclipse Editor to Apache CI server
>
>
> Key: DOXIATOOLS-11
> URL: https://jira.codehaus.org/browse/DOXIATOOLS-11
> Project: Maven Doxia Tools
> Issue Type: New Feature
> Components: Doxia Eclipse Editor
>Reporter: Herve Boutemy
> Attachments: doxia-osgi.log, typescript
>
>
> latest builds should be downloadable from
> https://builds.apache.org//view/M-R/view/Maven/
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (DOXIATOOLS-11) add Doxia Eclipse Editor to Apache CI server
[ https://jira.codehaus.org/browse/DOXIATOOLS-11?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy closed DOXIATOOLS-11. --- Resolution: Fixed Assignee: Herve Boutemy great, it is working! update site made by CI is at https://builds.apache.org/view/M-R/view/Maven/job/doxia-eclipse-editor/ws/doxia-ide-eclipse/eclipse-plugins/features/org.apache.maven.doxia.ide.eclipse.feature/target/site/ I just installed from this location into my Eclipse, and it works like a charm the icons are not there (only text), but freeze when editing has disappeared: this bug was the most critical one thank you Benson > add Doxia Eclipse Editor to Apache CI server > > > Key: DOXIATOOLS-11 > URL: https://jira.codehaus.org/browse/DOXIATOOLS-11 > Project: Maven Doxia Tools > Issue Type: New Feature > Components: Doxia Eclipse Editor >Reporter: Herve Boutemy >Assignee: Herve Boutemy > Attachments: doxia-osgi.log, typescript > > > latest builds should be downloadable from > https://builds.apache.org//view/M-R/view/Maven/ -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
