[jira] Created: (MNG-5189) Provide a way to specify module ordering when they are activated in profiles.
Provide a way to specify module ordering when they are activated in profiles.
-
Key: MNG-5189
URL: https://jira.codehaus.org/browse/MNG-5189
Project: Maven 2 3
Issue Type: Improvement
Components: Reactor and workspace
Reporter: Ondrej Zizka
In our project, sub-modules are activated in profiles.
However, due to unflexible way Maven orders profiles, it's not possible to
enforce certain submodule being run last. Only possibility is to move it one
level above.
My suggestion is to allow specifying modules order in which they would run iif
they are activated:
{code}
modulesOrder
modulemodule1module
modulemodule2module
otherModules/
modulelastButOneModule/module
modulelastModule/module
/modulesOrder
{code}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MINDEXER-44) NPE from DefaultSearchEngine.doSearchWithCeiling
[
https://jira.codehaus.org/browse/MINDEXER-44?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivier Lamy updated MINDEXER-44:
-
Fix Version/s: 4.1.3
Assignee: Olivier Lamy
NPE from DefaultSearchEngine.doSearchWithCeiling
Key: MINDEXER-44
URL: https://jira.codehaus.org/browse/MINDEXER-44
Project: Maven Indexer
Issue Type: Bug
Affects Versions: 4.1.1
Reporter: Jesse Glick
Assignee: Olivier Lamy
Priority: Minor
Fix For: 4.1.3
http://netbeans.org/bugzilla/show_bug.cgi?id=202138 reports
http://statistics.netbeans.org/exceptions/messageslog?id=533660 which shows
{code}
java.lang.NullPointerException
at
org.apache.maven.index.DefaultSearchEngine.doSearchWithCeiling(DefaultSearchEngine.java:316)
at
org.apache.maven.index.DefaultSearchEngine.searchFlat(DefaultSearchEngine.java:169)
at
org.apache.maven.index.DefaultSearchEngine.searchFlatPaged(DefaultSearchEngine.java:102)
at
org.apache.maven.index.DefaultSearchEngine.searchFlatPaged(DefaultSearchEngine.java:77)
{code}
This comes after some index download problems like
{code}
java.io.FileNotFoundException: Resource nexus-maven-repository-index.gz does
not exist
at
org.apache.maven.index.updater.WagonHelper$WagonFetcher.retrieve(WagonHelper.java:196)
at
org.apache.maven.index.updater.WagonHelper$WagonFetcher.retrieve(WagonHelper.java:166)
at
org.apache.maven.index.updater.DefaultIndexUpdater.loadIndexDirectory(DefaultIndexUpdater.java:191)
at
org.apache.maven.index.updater.DefaultIndexUpdater.access$300(DefaultIndexUpdater.java:76)
at
org.apache.maven.index.updater.DefaultIndexUpdater$LuceneIndexAdaptor.setIndexFile(DefaultIndexUpdater.java:642)
at
org.apache.maven.index.updater.DefaultIndexUpdater.fetchAndUpdateIndex(DefaultIndexUpdater.java:861)
at
org.apache.maven.index.updater.DefaultIndexUpdater.fetchAndUpdateIndex(DefaultIndexUpdater.java:157)
{code}
It seems that the {{DefaultIndexingContext.indexSearcher}} is null, for
whatever reason, and {{searchFlatPaged}} is not verifying that it has been
passed a valid context and does not attempt to fix an invalid context,
perhaps using {{openAndWarmupReaders}}.
Probably the caller is at fault for attempting a search on a context with no
valid index, but this ought to be reported more clearly than with an NPE
several calls down the stack, and there should be some documented method for
checking that a context is somehow complete and ready for use.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MSITE-617) Variable substitution in the site url doesn't work
[
https://jira.codehaus.org/browse/MSITE-617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=282499#comment-282499
]
Claus Nielsen commented on MSITE-617:
-
Tried this:
properties
project.build.sourceEncodingUTF-8/project.build.sourceEncoding
siteDeployUrlscp://mvn/data/Maven/sites/${project.artifactId}/${project.version}/siteDeployUrl
/properties
distributionManagement
site
idsites/id
nameProject Website/name
url${siteDeployUrl}/url
/site
/distributionManagement
With this result:
[INFO] [site:deploy {execution: default-cli}]
scp://mvn/data/Maven/sites/${project.artifactId}/${project.version}/ - Session:
Opened
[INFO] Pushing E:\tafe\workspace2\tafe\target\site
[INFO] to
scp://mvn/data/Maven/sites/${project.artifactId}/${project.version}/../../tafe/1.2.0-SNAPSHOT
Executing command: mkdir -p
/data/Maven/sites/${project.artifactId}/${project.version}/../../tafe/1.2.0-SNAPSHOT
scp://mvn/data/Maven/sites/${project.artifactId}/${project.version}/ - Session:
Disconnecting
scp://mvn/data/Maven/sites/${project.artifactId}/${project.version}/ - Session:
Disconnected
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Error uploading site
Embedded error: Error performing commands for file transfer
Exit code: 1 - bash:
/data/Maven/sites/${project.artifactId}/${project.version}/../../tafe/1.2.0-SNAPSHOT:
bad substitution
And this (different host name in the site URL):
properties
project.build.sourceEncodingUTF-8/project.build.sourceEncoding
siteDeployUrlscp://mXn/data/Maven/sites/${project.artifactId}/${project.version}/siteDeployUrl
/properties
distributionManagement
site
idsites/id
nameProject Website/name
url${siteDeployUrl}/url
/site
/distributionManagement
With this result:
[INFO] [site:deploy {execution: default-cli}]
scp://mvn/data/Maven/sites/${project.artifactId}/${project.version}/ - Session:
Opened
[INFO] Pushing E:\tafe\workspace2\tafe\target\site
[INFO] to
scp://mvn/data/Maven/sites/${project.artifactId}/${project.version}/../../../../../../mXn/data/Maven/sites/tafe/1.2.0-SNAPSHOT
Executing command: mkdir -p
/data/Maven/sites/${project.artifactId}/${project.version}/../../../../../../mXn/data/Maven/sites/tafe/1.2.0-SNAPSHOT
scp://mvn/data/Maven/sites/${project.artifactId}/${project.version}/ - Session:
Disconnecting
scp://mvn/data/Maven/sites/${project.artifactId}/${project.version}/ - Session:
Disconnected
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Error uploading site
Embedded error: Error performing commands for file transfer
Exit code: 1 - bash:
/data/Maven/sites/${project.artifactId}/${project.version}/../../../../../../mXn/data/Maven/sites/tafe/1.2.0-SNAPSHOT:
bad substitution
Variable substitution in the site url doesn't work
--
Key: MSITE-617
URL: https://jira.codehaus.org/browse/MSITE-617
Project: Maven 2.x and 3.x Site Plugin
Issue Type: Bug
Components: site:deploy
Affects Versions: 2.3
Environment: Windows 7 and RHEL6
Reporter: Claus Nielsen
site:deploy fails because variable substitution in the site url no longer
works (it did in version 2.2).
The distributionManagement section in out POM looks something like this:
distributionManagement
site
idsites/id
nameProject Website/name
urlscp://server/sites/${project.artifactId}/${project.version}/url
/site
/distributionManagement
Copying the site to the above mentioned url fails with this message:
[INFO] Error uploading site
Embedded error: Error performing commands for file transfer
Exit code: 1 - bash:
/sites/${project.artifactId}/${project.version}/../../id-of-the-artifact/0.2.8-SNAPSHOT:
bad substitution
Ie. the substitutiuon variables have not been substituted, instead the
property values have been appended to the url along with a few dots and
dashes.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Issue Comment Edited: (MSITE-617) Variable substitution in the site url doesn't work
[
https://jira.codehaus.org/browse/MSITE-617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=282499#comment-282499
]
Claus Nielsen edited comment on MSITE-617 at 11/1/11 4:27 AM:
--
Tried this:
properties
project.build.sourceEncodingUTF-8/project.build.sourceEncoding
siteDeployUrlscp://mvn/data/Maven/sites/${project.artifactId}/${project.version}/siteDeployUrl
/properties
distributionManagement
site
idsites/id
nameProject Website/name
url${siteDeployUrl}/url
/site
/distributionManagement
With this result:
[INFO] [site:deploy {execution: default-cli}]
scp://mvn/data/Maven/sites/${project.artifactId}/${project.version}/ - Session:
Opened
[INFO] Pushing E:\tafe\workspace2\tafe\target\site
[INFO] to
scp://mvn/data/Maven/sites/${project.artifactId}/${project.version}/../../tafe/1.2.0-SNAPSHOT
Executing command: mkdir -p
/data/Maven/sites/${project.artifactId}/${project.version}/../../tafe/1.2.0-SNAPSHOT
scp://mvn/data/Maven/sites/${project.artifactId}/${project.version}/ - Session:
Disconnecting
scp://mvn/data/Maven/sites/${project.artifactId}/${project.version}/ - Session:
Disconnected
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Error uploading site
Embedded error: Error performing commands for file transfer
Exit code: 1 - bash:
/data/Maven/sites/${project.artifactId}/${project.version}/../../tafe/1.2.0-SNAPSHOT:
bad substitution
And then changed the host name in the site URL:
properties
project.build.sourceEncodingUTF-8/project.build.sourceEncoding
siteDeployUrlscp://mXn/data/Maven/sites/${project.artifactId}/${project.version}/siteDeployUrl
/properties
distributionManagement
site
idsites/id
nameProject Website/name
url${siteDeployUrl}/url
/site
/distributionManagement
Then a new site:deploy gave this result (I didn't build the site again - just
ran site:deploy):
[INFO] [site:deploy {execution: default-cli}]
scp://mvn/data/Maven/sites/${project.artifactId}/${project.version}/ - Session:
Opened
[INFO] Pushing E:\tafe\workspace2\tafe\target\site
[INFO] to
scp://mvn/data/Maven/sites/${project.artifactId}/${project.version}/../../../../../../mXn/data/Maven/sites/tafe/1.2.0-SNAPSHOT
Executing command: mkdir -p
/data/Maven/sites/${project.artifactId}/${project.version}/../../../../../../mXn/data/Maven/sites/tafe/1.2.0-SNAPSHOT
scp://mvn/data/Maven/sites/${project.artifactId}/${project.version}/ - Session:
Disconnecting
scp://mvn/data/Maven/sites/${project.artifactId}/${project.version}/ - Session:
Disconnected
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Error uploading site
Embedded error: Error performing commands for file transfer
Exit code: 1 - bash:
/data/Maven/sites/${project.artifactId}/${project.version}/../../../../../../mXn/data/Maven/sites/tafe/1.2.0-SNAPSHOT:
bad substitution
was (Author: clanie):
Tried this:
properties
project.build.sourceEncodingUTF-8/project.build.sourceEncoding
siteDeployUrlscp://mvn/data/Maven/sites/${project.artifactId}/${project.version}/siteDeployUrl
/properties
distributionManagement
site
idsites/id
nameProject Website/name
url${siteDeployUrl}/url
/site
/distributionManagement
With this result:
[INFO] [site:deploy {execution: default-cli}]
scp://mvn/data/Maven/sites/${project.artifactId}/${project.version}/ - Session:
Opened
[INFO] Pushing E:\tafe\workspace2\tafe\target\site
[INFO] to
scp://mvn/data/Maven/sites/${project.artifactId}/${project.version}/../../tafe/1.2.0-SNAPSHOT
Executing command: mkdir -p
/data/Maven/sites/${project.artifactId}/${project.version}/../../tafe/1.2.0-SNAPSHOT
scp://mvn/data/Maven/sites/${project.artifactId}/${project.version}/ - Session:
Disconnecting
scp://mvn/data/Maven/sites/${project.artifactId}/${project.version}/ - Session:
Disconnected
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Error uploading site
Embedded error: Error performing commands for file transfer
Exit code: 1 - bash:
/data/Maven/sites/${project.artifactId}/${project.version}/../../tafe/1.2.0-SNAPSHOT:
bad substitution
And this (different host name in the site URL):
properties
project.build.sourceEncodingUTF-8/project.build.sourceEncoding
siteDeployUrlscp://mXn/data/Maven/sites/${project.artifactId}/${project.version}/siteDeployUrl
[jira] Commented: (MSANDBOX-51) Rewrite Plexus Utils classes at the ASF from scratch
[ https://jira.codehaus.org/browse/MSANDBOX-51?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=282507#comment-282507 ] Mark Struberg commented on MSANDBOX-51: --- patch applied, thanks James and Michael! Rewrite Plexus Utils classes at the ASF from scratch Key: MSANDBOX-51 URL: https://jira.codehaus.org/browse/MSANDBOX-51 Project: Maven 2.x Sandbox Issue Type: New Feature Reporter: Mark Struberg Attachments: diff.txt, plexus-utils-tck.patch, plexus-utils-tck.patch plexus-utils are 85% written by ASF committers, but we still don't have a IP cleared history. For cleaning this up we aim to rewrite those classes from scratch in ASF maven sandbox. The strategy is the following: 1. create unit tests for the existing plexus classes 2. create a new implementation from scratch 3. the new implementation must be a binary API compatible drop-in replacement -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MDEP-259) copy-dependencies fails with Error copying artifact from .../target/classes to .../classes
[
https://jira.codehaus.org/browse/MDEP-259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Veithen closed MDEP-259.
Resolution: Won't Fix
I had another look at the issue and it turns out that my proposed change no
longer works on Maven 3 because of some subtle changes in the behavior of
ArtifactResolver. I don't see any other way to get around this.
In my particular case (importing a complex multi-module build into Eclipse) I
now recommend users to do this with mvn -DskipTests=true install
eclipse:eclipse instead of mvn generate-test-resources eclipse:eclipse. The
drawback is that it increases the risk of getting into a chicken-and-egg
problem where one wants to refresh the Eclipse project to investigate a build
failure but it is not possible to do that because that build failure causes the
Maven command used to import the sources into Eclipse to fail...
copy-dependencies fails with Error copying artifact from .../target/classes
to .../classes
Key: MDEP-259
URL: https://jira.codehaus.org/browse/MDEP-259
Project: Maven 2.x Dependency Plugin
Issue Type: Bug
Components: copy-dependencies
Affects Versions: 2.0, 2.1
Environment: Maven 2.0.9
maven-dependency-plugin 2.0, 2.1 or 2.2-SNAPSHOT (r922616)
Reporter: Andreas Veithen
Assignee: Brian Fox
Attachments: patch.txt, test-project.zip
Scenario:
* dependency:copy-dependencies is used to copy a dependency artifact that is
part of the same multi-module build.
* The compile phase is executed, but not the package phase.
An example of this scenario is using maven-eclipse-plugin to import a Maven
project with generated test (re)sources. In this case, one would execute mvn
generate-test-resources eclipse:eclipse to make sure that the generated
(re)sources are imported into the workspace (by default, maven-eclipse-plugin
executes generate-sources and generate-resources, but not
generate-test-sources and generate-test-resources).
Result: The build fails with the following error:
[INFO] [dependency:copy-dependencies {execution: default}]
[INFO] Copying classes to
/Users/veithen/dev/maven/axis/axis2/modules/fastinfoset/target/repo/modules/classes
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Error copying artifact from
/Users/veithen/dev/maven/axis/axis2/modules/addressing/target/classes to
/Users/veithen/dev/maven/axis/axis2/modules/fastinfoset/target/repo/modules/classes
Embedded error:
/Users/veithen/dev/maven/axis/axis2/modules/addressing/target/classes (No
such file or directory)
Steps to reproduce:
* Unpack the attached test project and build the entire project once with
mvn install.
* Execute mvn generate-resources from the root project - success (because
the compile phase is not executed)
* Execute mvn package from the root project - success (because the package
phase is executed)
* Execute mvn generate-test-resources from the root project - fails
(because the compile phase is executed, but not the package phase)
* Execute mvn generate-test-resources in project2 - success (because the
dependency is not part of the same build)
Root cause analysis: In the scenario described above (compile phase executed,
package phase not executed), Artifact#getFile() points to the target/classes
directory instead of the output artifact. dependency:copy-dependencies
doesn't detect this situation and blindly attempts to execute the copy
operation. This fails with the error message shown above. Note that even if
the operation didn't fail, it would produce an unexpected result.
Proposed fix (see attached patch): Change maven-dependency-plugin to detect
this situation and let it replace the original Artifact object by a new one
resolved from the repository (which would then refer to the artifact
generated by a previous build, exactly as in the mvn generate-resources case).
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SUREFIRE-329) Support for JUNIT extensions
[ https://jira.codehaus.org/browse/SUREFIRE-329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=282509#comment-282509 ] nkeywal commented on SUREFIRE-329: -- Kristian: Could you share the result of the tests you mentioned on the Aug. 29th? If the tests are ok, is it a feature you plan to integrate soon? Thank you! :-) Support for JUNIT extensions Key: SUREFIRE-329 URL: https://jira.codehaus.org/browse/SUREFIRE-329 Project: Maven Surefire Issue Type: Wish Components: Junit 4.x support Reporter: Anuj Kathuria Assignee: Kristian Rosenvold Fix For: Backlog Attachments: surefire-329.txt, surefire-329.txt Is there any plan to support using JUNIT extensions such as @Category,@PreRequisite with Maven2 SureFire plugin? The JUNIT EXTENSION URL: http://www.junitext.org/ We would like to specify the categories to run via a configurable option in the maven surefire plugin that supports JUNIT extensions See example Java Code: The following runs only tests with Category - Z. //In JUnit4 JUnitCore core = new JUnitCore(); // use for categories special listener, give some statistics core.addListener(new CategoryTextListener(System.out)); Request req = Request.aClass(SpcfTest.class); core.run(req.filterWith(new CategoryFilter(Z))); -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MDEP-259) copy-dependencies fails with Error copying artifact from .../target/classes to .../classes
[
https://jira.codehaus.org/browse/MDEP-259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=282520#comment-282520
]
Gili commented on MDEP-259:
---
What about the use-case I posted? Shouldn't Maven give a better error message
when I refer to a non-existent artifact (missing a classifier)?
copy-dependencies fails with Error copying artifact from .../target/classes
to .../classes
Key: MDEP-259
URL: https://jira.codehaus.org/browse/MDEP-259
Project: Maven 2.x Dependency Plugin
Issue Type: Bug
Components: copy-dependencies
Affects Versions: 2.0, 2.1
Environment: Maven 2.0.9
maven-dependency-plugin 2.0, 2.1 or 2.2-SNAPSHOT (r922616)
Reporter: Andreas Veithen
Assignee: Brian Fox
Attachments: patch.txt, test-project.zip
Scenario:
* dependency:copy-dependencies is used to copy a dependency artifact that is
part of the same multi-module build.
* The compile phase is executed, but not the package phase.
An example of this scenario is using maven-eclipse-plugin to import a Maven
project with generated test (re)sources. In this case, one would execute mvn
generate-test-resources eclipse:eclipse to make sure that the generated
(re)sources are imported into the workspace (by default, maven-eclipse-plugin
executes generate-sources and generate-resources, but not
generate-test-sources and generate-test-resources).
Result: The build fails with the following error:
[INFO] [dependency:copy-dependencies {execution: default}]
[INFO] Copying classes to
/Users/veithen/dev/maven/axis/axis2/modules/fastinfoset/target/repo/modules/classes
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Error copying artifact from
/Users/veithen/dev/maven/axis/axis2/modules/addressing/target/classes to
/Users/veithen/dev/maven/axis/axis2/modules/fastinfoset/target/repo/modules/classes
Embedded error:
/Users/veithen/dev/maven/axis/axis2/modules/addressing/target/classes (No
such file or directory)
Steps to reproduce:
* Unpack the attached test project and build the entire project once with
mvn install.
* Execute mvn generate-resources from the root project - success (because
the compile phase is not executed)
* Execute mvn package from the root project - success (because the package
phase is executed)
* Execute mvn generate-test-resources from the root project - fails
(because the compile phase is executed, but not the package phase)
* Execute mvn generate-test-resources in project2 - success (because the
dependency is not part of the same build)
Root cause analysis: In the scenario described above (compile phase executed,
package phase not executed), Artifact#getFile() points to the target/classes
directory instead of the output artifact. dependency:copy-dependencies
doesn't detect this situation and blindly attempts to execute the copy
operation. This fails with the error message shown above. Note that even if
the operation didn't fail, it would produce an unexpected result.
Proposed fix (see attached patch): Change maven-dependency-plugin to detect
this situation and let it replace the original Artifact object by a new one
resolved from the repository (which would then refer to the artifact
generated by a previous build, exactly as in the mvn generate-resources case).
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MACR-3) Maven site should has an example with adding Main Class
Maven site should has an example with adding Main Class --- Key: MACR-3 URL: https://jira.codehaus.org/browse/MACR-3 Project: Maven ACR Plugin Issue Type: Improvement Affects Versions: 1.0 Reporter: Gustavo Orair Maven ACR plugin should confirm if the resulting Manifest contain a setting for Main-Class, because The Java EE spec requires that app clients specify the main class (http://www.java.net/forum/topic/glassfish/glassfish/problems-using-java-web-start-application-client-libraries-not-found). If Manifest does not contain Main-Class a warning should be emitted. Also, It would be very valuable if some examples specifying Main-Class are added to the site http://maven.apache.org/plugins/maven-acr-plugin/. In actual configuration, users tend to create application clients without Main-Class and may get strange errors while trying to launch the application client. One example of these errors, may be accessed in: http://www.java.net/forum/topic/glassfish/glassfish/problems-using-java-web-start-application-client-libraries-not-found -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MINDEXER-45) WagonFetcher.disconnect should throw IOException
WagonFetcher.disconnect should throw IOException
Key: MINDEXER-45
URL: https://jira.codehaus.org/browse/MINDEXER-45
Project: Maven Indexer
Issue Type: Bug
Affects Versions: 4.1.2
Reporter: Jesse Glick
Priority: Minor
{{WagonHelper.WagonFetcher.disconnect}} catches {{ConnectionException}} and
logs it, but does not throw anything. Since the interface method is documented
to throw {{IOException}}, it should rather rethrow the exception.
{code}
diff --git
a/indexer-core/src/main/java/org/apache/maven/index/updater/WagonHelper.java
b/indexer-core/src/main/java/org/apache/maven/index/updater/WagonHelper.java
index 399dd83..79f3606 100644
--- a/indexer-core/src/main/java/org/apache/maven/index/updater/WagonHelper.java
+++ b/indexer-core/src/main/java/org/apache/maven/index/updater/WagonHelper.java
@@ -145,6 +145,7 @@ public class WagonHelper
}
public void disconnect()
+throws IOException
{
if ( wagon != null )
{
@@ -154,7 +155,9 @@ public class WagonHelper
}
catch ( ConnectionException ex )
{
-logError( Failed to close connection, ex );
+IOException ioe = new IOException( ex.toString() );
+ioe.initCause( ex );
+throw ioe;
}
}
}
{code}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MNG-5190) Guide to Coping with Sun JARs has obsolete recommendations
Guide to Coping with Sun JARs has obsolete recommendations Key: MNG-5190 URL: https://jira.codehaus.org/browse/MNG-5190 Project: Maven 2 3 Issue Type: Bug Components: Documentation: Guides Reporter: Jesse Glick http://maven.apache.org/guides/mini/guide-coping-with-sun-jars.html has a section beginning Note: Java.net provides a Maven 2 repository which is obsolete, since these artifacts are now in Central. The whole page is suspect and should perhaps be removed; at least some of the mentioned artifacts are available in Central. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (DOXIASITETOOLS-62) improve breadcrumbs inheritance: if child defines an item already in parent, remove every breadcrumb item from parent after it
[ https://jira.codehaus.org/browse/DOXIASITETOOLS-62?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy closed DOXIASITETOOLS-62. --- Resolution: Fixed Fix Version/s: 1.2.1 Assignee: Herve Boutemy done in [r1196128|http://svn.apache.org/viewvc?rev=1196128view=rev] improve breadcrumbs inheritance: if child defines an item already in parent, remove every breadcrumb item from parent after it -- Key: DOXIASITETOOLS-62 URL: https://jira.codehaus.org/browse/DOXIASITETOOLS-62 Project: Maven Doxia Sitetools Issue Type: Improvement Components: Decoration model Affects Versions: 1.2 Reporter: Herve Boutemy Assignee: Herve Boutemy Fix For: 1.2.1 see MSITE-582 suppose parent descriptor has following breacrumb items: A B C D E F I want a child to remove D E F and replace with M N O A B C M N O To do that, that child should define C M N O C is found in parent breadcrumb items, then we can delete the following parent items then add following child items -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (DOXIA-375) Locales and Encoding params are ignored by plugin
[
https://jira.codehaus.org/browse/DOXIA-375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Herve Boutemy updated DOXIA-375:
Description:
I'm using doxia-maven-plugin to generate the project documentation site.
This is the plugin session of my pom.xml:
{code:xml} ...
properties
project.build.sourceEncodingUTF-8/project.build.sourceEncoding
project.reporting.outputEncodingUTF-8
/project.reporting.outputEncoding
/properties
...
plugin
groupIdorg.apache.maven.doxia/groupId
artifactIddoxia-maven-plugin/artifactId
version1.1.2/version
executions
execution
phasepre-site/phase
goals
goalrender-books/goal
/goals
/execution
/executions
configuration
localespt_BR/locales
inputEncoding${project.build.sourceEncoding}/inputEncoding
outputEncoding${project.reporting.outputEncoding}
/outputEncoding
books
book
directorysrc/site/directory
descriptorsrc/site/book-reference.xml/descriptor
formats
format
idxdoc/id
/format
/formats
/book
/books
/configuration
/plugin
...{code}
The content auto-generated by the plugin presents two problems:
1) The locale pt_br was ignored, generating words in english instead of
brazilian portuguese;
2) The encoding UFT-8 was apparently ignored too, generating unwished chars;
{noformat}Next: Configurações
Referência - Table Of Content
Configurações
Servidor
Introdu#8730;ß#8730;£o
Administra#8730;ß#8730;£o
E-mail
Banco de Dados
Base de Usu#8730;°rios
Base LDAP
Base Personalizada
Agente
Introdu#8730;ß#8730;£o
Next: Configurações{noformat}
was:
I'm using doxia-maven-plugin to generate the project documentation site.
This is the plugin session of my pom.xml:
...
properties
project.build.sourceEncodingUTF-8/project.build.sourceEncoding
project.reporting.outputEncodingUTF-8
/project.reporting.outputEncoding
/properties
...
plugin
groupIdorg.apache.maven.doxia/groupId
artifactIddoxia-maven-plugin/artifactId
version1.1.2/version
executions
execution
phasepre-site/phase
goals
goalrender-books/goal
/goals
/execution
/executions
configuration
localespt_BR/locales
inputEncoding${project.build.sourceEncoding}/inputEncoding
outputEncoding${project.reporting.outputEncoding}
/outputEncoding
books
book
directorysrc/site/directory
descriptorsrc/site/book-reference.xml/descriptor
formats
format
[jira] Updated: (DOXIA-380) Use of #include in APT page causes NullPointerException during page rendering
[
https://jira.codehaus.org/browse/DOXIA-380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Herve Boutemy updated DOXIA-380:
Description:
In the last 2 days I tried to get this thing working.
The situation is the following: I'm working on a maven site project and, for
some pages, I'm currently using the APT format.
I'd really like to be able to include existing APT pages inside an APT page, in
order to make the collaboration between the 4 members of the project much
easier and smoother.
To give an idea, I'd like to do this:
merged-page.apt:
{noformat} ---
Title
---
---
---
Develeper 1 proposal:
include page 1
Developer 2 proposal:
include page 2
etc.{noformat}
At first, I tried using the %snippet DOXIA macro, but the included APT page
would not be rendered to HTML even setting verbatim=false.
Then, I tried the #include macro from Velocity. I renamed my APT file to
filename.apt.vm in order to trigger the Velocity processor on it and put the
#include line in the file, but, whenever I launch maven site I keep getting
this error:
and the page is not generated.
Is there a way to fix this?
was:
In the last 2 days I tried to get this thing working.
The situation is the following: I'm working on a maven site project and, for
some pages, I'm currently using the APT format.
I'd really like to be able to include existing APT pages inside an APT page, in
order to make the collaboration between the 4 members of the project much
easier and smoother.
To give an idea, I'd like to do this:
merged-page.apt:
---
Title
---
---
---
Develeper 1 proposal:
include page 1
Developer 2 proposal:
include page 2
etc.
At first, I tried using the %snippet DOXIA macro, but the included APT page
would not be rendered to HTML even setting verbatim=false.
Then, I tried the #include macro from Velocity. I renamed my APT file to
filename.apt.vm in order to trigger the Velocity processor on it and put the
#include line in the file, but, whenever I launch maven site I keep getting
this error:
and the page is not generated.
Is there a way to fix this?
Use of #include in APT page causes NullPointerException during page rendering
-
Key: DOXIA-380
URL: https://jira.codehaus.org/browse/DOXIA-380
Project: Maven Doxia
Issue Type: Bug
Components: Site Renderer
Environment: maven 2.2.1
Reporter: Alan Alberghini
Priority: Minor
Attachments: apt-include.log, VelocityTest.tar.gz
In the last 2 days I tried to get this thing working.
The situation is the following: I'm working on a maven site project and, for
some pages, I'm currently using the APT format.
I'd really like to be able to include existing APT pages inside an APT page,
in order to make the collaboration between the 4 members of the project much
easier and smoother.
To give an idea, I'd like to do this:
merged-page.apt:
{noformat} ---
Title
---
---
---
Develeper 1 proposal:
include page 1
Developer 2 proposal:
include page 2
etc.{noformat}
At first, I tried using the %snippet DOXIA macro, but the included APT page
would not be rendered to HTML even setting verbatim=false.
Then, I tried the #include macro from Velocity. I renamed my APT file to
filename.apt.vm in order to trigger the Velocity processor on it and put the
#include line in the file, but, whenever I launch maven site I keep getting
this error:
and the page is not generated.
Is there a way to fix this?
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (DOXIA-453) ArrayIndexOutOfBoundsException
[
https://jira.codehaus.org/browse/DOXIA-453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Herve Boutemy updated DOXIA-453:
Description:
If you checkout the tag for version 1.7 of the maven antrun plugin, and run
mvn site site:stage-deploy -Preporting
you will be rewarded with the below. Oddly, when I ran it a second time with -X
it went away.
{noformat}[ERROR] FATAL ERROR
[INFO]
[INFO] 1
[INFO]
[INFO] Trace
java.lang.ArrayIndexOutOfBoundsException: 1
at
org.apache.maven.doxia.module.apt.AptParser$Table.traverseRow(AptParser.java:2618)
at
org.apache.maven.doxia.module.apt.AptParser$Table.traverse(AptParser.java:2433)
at
org.apache.maven.doxia.module.apt.AptParser.traverseSectionBlocks(AptParser.java:861)
at
org.apache.maven.doxia.module.apt.AptParser.traverseSection(AptParser.java:807)
at
org.apache.maven.doxia.module.apt.AptParser.traverseSection(AptParser.java:816)
at
org.apache.maven.doxia.module.apt.AptParser.traverseBody(AptParser.java:758)
at org.apache.maven.doxia.module.apt.AptParser.parse(AptParser.java:228)
at org.apache.maven.doxia.DefaultDoxia.parse(DefaultDoxia.java:63)
at
org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderDocument(DefaultSiteRenderer.java:399)
at
org.apache.maven.doxia.siterenderer.DoxiaDocumentRenderer.renderDocument(DoxiaDocumentRenderer.java:53)
at
org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule(DefaultSiteRenderer.java:317)
at
org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:134)
at
org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:175)
at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:138)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
at
org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
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)
[INFO]
{noformat}
was:
If you checkout the tag for version 1.7 of the maven antrun plugin, and run
mvn site site:stage-deploy -Preporting
you will be rewarded with the below. Oddly, when I ran it a second time with -X
it went away.
[ERROR] FATAL ERROR
[INFO]
[INFO] 1
[INFO]
[INFO] Trace
java.lang.ArrayIndexOutOfBoundsException: 1
at
org.apache.maven.doxia.module.apt.AptParser$Table.traverseRow(AptParser.java:2618)
at
org.apache.maven.doxia.module.apt.AptParser$Table.traverse(AptParser.java:2433)
at
org.apache.maven.doxia.module.apt.AptParser.traverseSectionBlocks(AptParser.java:861)
at
org.apache.maven.doxia.module.apt.AptParser.traverseSection(AptParser.java:807)
at
org.apache.maven.doxia.module.apt.AptParser.traverseSection(AptParser.java:816)
at
org.apache.maven.doxia.module.apt.AptParser.traverseBody(AptParser.java:758)
at org.apache.maven.doxia.module.apt.AptParser.parse(AptParser.java:228)
at org.apache.maven.doxia.DefaultDoxia.parse(DefaultDoxia.java:63)
at
[jira] Commented: (DOXIA-405) The generated xhtml document has the entire content on a single line
[ https://jira.codehaus.org/browse/DOXIA-405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=282549#comment-282549 ] Herve Boutemy commented on DOXIA-405: - ok, real pretty printing, with indentation, should be done outsite But having some newlines is useful The generated xhtml document has the entire content on a single line Key: DOXIA-405 URL: https://jira.codehaus.org/browse/DOXIA-405 Project: Maven Doxia Issue Type: Improvement Components: Module - Xhtml Affects Versions: 1.1.3 Environment: Maven Site Plugin 2.1.1 Windows XP Pro Reporter: Dennis Lundberg If you view the source for http://maven.apache.org/plugins/index.html, you will see that the entire content is on line 207 and is 35396 columns wide. Trying to debug such a page is near impossible. For very large documents is isn't even possible for some browsers to show the source with that many columns. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MDEP-325) build-classpath adds a newline character when dependency artifact name starts with letter n
[
https://jira.codehaus.org/browse/MDEP-325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=282556#comment-282556
]
Thomas Gran commented on MDEP-325:
--
I am trying to inject (using filtering) the classpath into a fitnesse
content.txt file (more on this later). I get simular errors. When a properties
file is read by Java the '\n' is translated the same way as in Java Strings, so
is '\r', '\t', '\f' ... as well as '\012' and '\u0020'. This is nice and make
it simple to inject new lines as well as other specal characters. But setting
the fileSeparator and pathSeparator does not work correct:
Example:
fileSeparator//fileSeparator
pathSeparator\n/pathSeparator
Should produce:
___
C:/myrepo/org/a/a-1.0.jar
C:/myrepo/org/b/b-1.0.jar
^^^
but instead I get:
___
C:/myrepo/org/a/a-1.0.jar/nC:/myrepo/org/b/b-1.0.jar
^^^
All '\' (not only File.separator) is replaced.
When generating a properties file the File.separator should by default be '\\'
on windows and '/' on Unix.
Note! When generating a fitness classpath I also need to insert whitespace
(both new lines and space). Since whitespace is trimed of xml elements (even
CDATA) it is important for me to keep the translation of the '\' character when
loading the properties file.
HOWTO ON FITNESS:
Here is how a fitness classpath could be generated:
content.txt:
|!contents -g|
!path ${classpath}
!path ../../target/classes
maven-dependency-plugin config:
fileSeparator//fileSeparator
pathSeparator\n!path\u0020/pathSeparator
outputFilterFiletrue/outputFilterFile
outputFilemyFilter.properties/outputFile
And then set up resource filtering ...
build-classpath adds a newline character when dependency artifact name starts
with letter n
---
Key: MDEP-325
URL: https://jira.codehaus.org/browse/MDEP-325
Project: Maven 2.x Dependency Plugin
Issue Type: Bug
Components: build-classpath
Affects Versions: 2.1, 2.2, 2.3
Reporter: L. Compère
Assignee: Brian Fox
I'm using a combination of the maven-dependency-plugin and the
maven-assembly-plugin to insert a classpath in a filtered resource.
It so happens that one of the dependencies to be added to the classpath is
neethi-2.0.4.jar.
The build-classpath goal of the dependency plugin writes the following in a
file (all on one line):
classpath=%MM_ENV_PATH%J/Lib/\httpcore-nio-4.0-beta1.jar;%MM_ENV_PATH%J/Lib/\neethi-2.0.4.jar;%MM_ENV_PATH%J/Lib/\axiom-api-1.2.7.jar;%MM_ENV_PATH%J/Lib/\axiom-dom-1.2.7.jar;
When the assembly plugin uses the content of the file generated by the
build-classpath goal of the dependency plugin, it translates the \n found in
%MM_ENV_PATH%J/Lib/\neethi-2.0.4.jar; into a NEWLINE character... causing
my classpath to be broken as such (on two lines):
%MM_ENV_PATH%J/Lib/\httpcore-nio-4.0-beta1.jar;%MM_ENV_PATH%J/Lib/
eethi-2.0.4.jar;%MM_ENV_PATH%J/Lib/\axiom-api-1.2.7.jar;%MM_ENV_PATH%J/Lib/\axiom-dom-1.2.7.jar;
notice how neethi-2.0.4.jar has become eethi-2.0.4.jar
Has anyone had such a problem?
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MDEP-325) build-classpath adds a newline character when dependency artifact name starts with letter n
[
https://jira.codehaus.org/browse/MDEP-325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=282558#comment-282558
]
Thomas Gran commented on MDEP-325:
--
I ment,
{noformat}
When generating a properties file the File.separator should by default be '\\'
on windows and '/' on Unix.
{noformat}
build-classpath adds a newline character when dependency artifact name starts
with letter n
---
Key: MDEP-325
URL: https://jira.codehaus.org/browse/MDEP-325
Project: Maven 2.x Dependency Plugin
Issue Type: Bug
Components: build-classpath
Affects Versions: 2.1, 2.2, 2.3
Reporter: L. Compère
Assignee: Brian Fox
I'm using a combination of the maven-dependency-plugin and the
maven-assembly-plugin to insert a classpath in a filtered resource.
It so happens that one of the dependencies to be added to the classpath is
neethi-2.0.4.jar.
The build-classpath goal of the dependency plugin writes the following in a
file (all on one line):
classpath=%MM_ENV_PATH%J/Lib/\httpcore-nio-4.0-beta1.jar;%MM_ENV_PATH%J/Lib/\neethi-2.0.4.jar;%MM_ENV_PATH%J/Lib/\axiom-api-1.2.7.jar;%MM_ENV_PATH%J/Lib/\axiom-dom-1.2.7.jar;
When the assembly plugin uses the content of the file generated by the
build-classpath goal of the dependency plugin, it translates the \n found in
%MM_ENV_PATH%J/Lib/\neethi-2.0.4.jar; into a NEWLINE character... causing
my classpath to be broken as such (on two lines):
%MM_ENV_PATH%J/Lib/\httpcore-nio-4.0-beta1.jar;%MM_ENV_PATH%J/Lib/
eethi-2.0.4.jar;%MM_ENV_PATH%J/Lib/\axiom-api-1.2.7.jar;%MM_ENV_PATH%J/Lib/\axiom-dom-1.2.7.jar;
notice how neethi-2.0.4.jar has become eethi-2.0.4.jar
Has anyone had such a problem?
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (DOXIA-405) The generated xhtml document has the entire content on a single line
[
https://jira.codehaus.org/browse/DOXIA-405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=282564#comment-282564
]
Herve Boutemy commented on DOXIA-405:
-
tried to implement it.
The feature is easy to do:
{noformat}
Index: src/main/java/org/apache/maven/doxia/sink/AbstractXmlSink.java
===
--- src/main/java/org/apache/maven/doxia/sink/AbstractXmlSink.java
(revision 1196075)
+++ src/main/java/org/apache/maven/doxia/sink/AbstractXmlSink.java
(working copy)
@@ -107,6 +107,12 @@
}
StringBuilder sb = new StringBuilder();
+
+if ( t.isBlock() )
+{
+sb.append( EOL );
+}
+
sb.append( LESS_THAN );
if ( nameSpace != null )
{noformat}
The generated xhtml document has the entire content on a single line
Key: DOXIA-405
URL: https://jira.codehaus.org/browse/DOXIA-405
Project: Maven Doxia
Issue Type: Improvement
Components: Module - Xhtml
Affects Versions: 1.1.3
Environment: Maven Site Plugin 2.1.1
Windows XP Pro
Reporter: Dennis Lundberg
If you view the source for http://maven.apache.org/plugins/index.html, you
will see that the entire content is on line 207 and is 35396 columns wide.
Trying to debug such a page is near impossible.
For very large documents is isn't even possible for some browsers to show the
source with that many columns.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Issue Comment Edited: (DOXIA-405) The generated xhtml document has the entire content on a single line
[
https://jira.codehaus.org/browse/DOXIA-405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=282564#comment-282564
]
Herve Boutemy edited comment on DOXIA-405 at 11/1/11 4:28 PM:
--
tried to implement it.
The feature is easy to do:
{noformat}
Index: src/main/java/org/apache/maven/doxia/sink/AbstractXmlSink.java
===
--- src/main/java/org/apache/maven/doxia/sink/AbstractXmlSink.java
(revision 1196075)
+++ src/main/java/org/apache/maven/doxia/sink/AbstractXmlSink.java
(working copy)
@@ -107,6 +107,12 @@
}
StringBuilder sb = new StringBuilder();
+
+if ( t.isBlock() )
+{
+sb.append( EOL );
+}
+
sb.append( LESS_THAN );
if ( nameSpace != null )
{noformat}
There are quite a few sink test methods to fix, add EOL ad trimming some
results: easy too
But there is a hard part: identity tests are severely affected, since the
newline adds some text before blocks
I'm stuck...
was (Author: hboutemy):
tried to implement it.
The feature is easy to do:
{noformat}
Index: src/main/java/org/apache/maven/doxia/sink/AbstractXmlSink.java
===
--- src/main/java/org/apache/maven/doxia/sink/AbstractXmlSink.java
(revision 1196075)
+++ src/main/java/org/apache/maven/doxia/sink/AbstractXmlSink.java
(working copy)
@@ -107,6 +107,12 @@
}
StringBuilder sb = new StringBuilder();
+
+if ( t.isBlock() )
+{
+sb.append( EOL );
+}
+
sb.append( LESS_THAN );
if ( nameSpace != null )
{noformat}
The generated xhtml document has the entire content on a single line
Key: DOXIA-405
URL: https://jira.codehaus.org/browse/DOXIA-405
Project: Maven Doxia
Issue Type: Improvement
Components: Module - Xhtml
Affects Versions: 1.1.3
Environment: Maven Site Plugin 2.1.1
Windows XP Pro
Reporter: Dennis Lundberg
If you view the source for http://maven.apache.org/plugins/index.html, you
will see that the entire content is on line 207 and is 35396 columns wide.
Trying to debug such a page is near impossible.
For very large documents is isn't even possible for some browsers to show the
source with that many columns.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MJAVADOC-333) Diacritics (accents) in project path prevent the plugin from working on Windows.
Diacritics (accents) in project path prevent the plugin from working on Windows. Key: MJAVADOC-333 URL: https://jira.codehaus.org/browse/MJAVADOC-333 Project: Maven 2.x Javadoc Plugin Issue Type: Bug Affects Versions: 2.8, 2.7 Environment: Win7 Reporter: Martin Pecka Priority: Critical My project is located in E:\Programování\Java\beam-3D-data-viewer. Notice the diacritics in the path. When launching the javadoc:javadoc goal, the build fails: . . . [ERROR] javadoc: warning - No source files for package org.esa.beam.util [ERROR] javadoc: error - No public or protected classes found to document. I looked on the generated options file, and that's the problem. Windows apparentely don't have their filenames encoded in UTF8 when passing them to the command line, but the options file is saved in UTF8. That's the reason why the plugin cannot find the source files. When I manually edit the file and save it in cp1250 encoding, running javadoc.bat works perfectly. This should obviously be fixed, but is there a quick workaround? Eg. a way to alter the generated javadoc.bat to prepend a call to iconv or something else. Now I can use the generated files, manually edit the options file, and run the task, but if I want to run the jar goal, this bug makes it impossible. Thanks for cooperation! -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
