[jira] [Created] (SUREFIRE-1760) Unbalanced number of test executions in forks (forkCount>1) results in no performance gain for jupiter/JUnit5 tests
Vlad Skarzhevskyy created SUREFIRE-1760:
---
Summary: Unbalanced number of test executions in forks
(forkCount>1) results in no performance gain for jupiter/JUnit5 tests
Key: SUREFIRE-1760
URL: https://issues.apache.org/jira/browse/SUREFIRE-1760
Project: Maven Surefire
Issue Type: Bug
Components: JUnit 5.x support
Reporter: Vlad Skarzhevskyy
Running JUnit5 tests using maven-surefire-plugin with
true e.g. mvn -DforkCount=8
Results: number of tests in each fork is significantly unbalanced, *+some forks
do not get tests at all+*..
The end results is that on CI server the total test execution will take as long
as longest fork and only 50% of the available resources are used.
In our case we observed that our 3000 integration tests after migration to
junit5 take 30 minutes insteads of 18 minutes as it was with junit 4.
The balance is restored when running with reuseForks=false but this will cause
additional overhead for complex integrations tests
e.g. tests requiring additional setup , classpath scanning and so on..
The results are similar with maven-surefire-plugin: 2.22.1, 2.22.2, 3.0.0-M4
Maven 3.6.3 , openjdk version "1.8.0_242" on Linux
BTW If junit-vintage-engine is used the same results observed for JUnit3 and
JUnit4 tests.
Consider example of 100 tests (10 classes 10 tests in each)
[https://github.com/skarzhevskyy/range-junit/tree/master/range-junit5-surefire-fork]
When running mvn -DforkCount=8 with extension that prints the number of tests
executed in each fork getting following:
{quote}Tests completed JVM Fork 8; total tests: 0; classes: 0
Tests completed JVM Fork 4; total tests: 0; classes: 0
Tests completed JVM Fork 1; total tests: 0; classes: 0
Tests completed JVM Fork 6; total tests: 0; classes: 0
Tests completed JVM Fork 3; total tests: 0; classes: 0
Tests completed JVM Fork 2; total tests: 0; classes: 0
Tests completed JVM Fork 7; total tests: 30; classes: 3
Tests completed JVM Fork 5; total tests: 70; classes: 7{quote}
mvn -DforkCount=4
{quote}Tests completed JVM Fork 2; total tests: 0; classes: 0
Tests completed JVM Fork 3; total tests: 10; classes: 1
Tests completed JVM Fork 4; total tests: 40; classes: 4
Tests completed JVM Fork 1; total tests: 50; classes: 5{quote}
The distribution is also random, results may vary between maven runs:
mvn -DforkCount=4
{quote}Tests completed JVM Fork 4; total tests: 0; classes: 0
Tests completed JVM Fork 2; total tests: 10; classes: 1
Tests completed JVM Fork 1; total tests: 30; classes: 3
Tests completed JVM Fork 3; total tests: 60; classes: 6{quote}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (SUREFIRE-1760) Unbalanced number of test executions in forks (forkCount>1) results in no performance gain for jupiter/JUnit5 tests
[
https://issues.apache.org/jira/browse/SUREFIRE-1760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vlad Skarzhevskyy updated SUREFIRE-1760:
Description:
Running JUnit5 tests using maven-surefire-plugin with
true e.g. mvn -DforkCount=8
Results: number of tests in each fork is significantly unbalanced, *+some forks
do not get tests at all+*..
The end results is that on CI server the total test execution will take as long
as longest fork and only 50% of the available resources are used.
In our case we observed that our 3000 integration tests after migration to
junit5 take 30 minutes insteads of 18 minutes as it was with junit 4.
The balance is restored when running with reuseForks=false but this will cause
additional overhead for complex integrations tests
e.g. tests requiring additional setup , classpath scanning and so on..
The results are similar with maven-surefire-plugin: 2.22.1, 2.22.2, 3.0.0-M4
Maven 3.6.3 , openjdk version "1.8.0_242" on Linux
BTW If junit-vintage-engine is used the same results observed for JUnit3 and
JUnit4 tests.
Consider example of 100 tests (10 classes 10 tests in each)
[https://github.com/skarzhevskyy/range-junit/tree/master/range-junit5-surefire-fork]
When running mvn -DforkCount=8 with extension that prints the number of tests
executed in each fork getting following:
{quote}Tests completed JVM Fork 8; total tests: 0; classes: 0
Tests completed JVM Fork 4; total tests: 0; classes: 0
Tests completed JVM Fork 1; total tests: 0; classes: 0
Tests completed JVM Fork 6; total tests: 0; classes: 0
Tests completed JVM Fork 3; total tests: 0; classes: 0
Tests completed JVM Fork 2; total tests: 0; classes: 0
Tests completed JVM Fork 7; total tests: 30; classes: 3
Tests completed JVM Fork 5; total tests: 70; classes: 7
{quote}
mvn -DforkCount=4
{quote}Tests completed JVM Fork 2; total tests: 0; classes: 0
Tests completed JVM Fork 3; total tests: 10; classes: 1
Tests completed JVM Fork 4; total tests: 40; classes: 4
Tests completed JVM Fork 1; total tests: 50; classes: 5
{quote}
The distribution is also random, results may vary between maven runs:
mvn -DforkCount=4
{quote}Tests completed JVM Fork 4; total tests: 0; classes: 0
Tests completed JVM Fork 2; total tests: 10; classes: 1
Tests completed JVM Fork 1; total tests: 30; classes: 3
Tests completed JVM Fork 3; total tests: 60; classes: 6
{quote}
was:
Running JUnit5 tests using maven-surefire-plugin with
true e.g. mvn -DforkCount=8
Results: number of tests in each fork is significantly unbalanced, *+some forks
do not get tests at all+*..
The end results is that on CI server the total test execution will take as long
as longest fork and only 50% of the available resources are used.
In our case we observed that our 3000 integration tests after migration to
junit5 take 30 minutes insteads of 18 minutes as it was with junit 4.
The balance is restored when running with reuseForks=false but this will cause
additional overhead for complex integrations tests
e.g. tests requiring additional setup , classpath scanning and so on..
The results are similar with maven-surefire-plugin: 2.22.1, 2.22.2, 3.0.0-M4
Maven 3.6.3 , openjdk version "1.8.0_242" on Linux
BTW If junit-vintage-engine is used the same results observed for JUnit3 and
JUnit4 tests.
Consider example of 100 tests (10 classes 10 tests in each)
[https://github.com/skarzhevskyy/range-junit/tree/master/range-junit5-surefire-fork]
When running mvn -DforkCount=8 with extension that prints the number of tests
executed in each fork getting following:
{quote}Tests completed JVM Fork 8; total tests: 0; classes: 0
Tests completed JVM Fork 4; total tests: 0; classes: 0
Tests completed JVM Fork 1; total tests: 0; classes: 0
Tests completed JVM Fork 6; total tests: 0; classes: 0
Tests completed JVM Fork 3; total tests: 0; classes: 0
Tests completed JVM Fork 2; total tests: 0; classes: 0
Tests completed JVM Fork 7; total tests: 30; classes: 3
Tests completed JVM Fork 5; total tests: 70; classes: 7{quote}
mvn -DforkCount=4
{quote}Tests completed JVM Fork 2; total tests: 0; classes: 0
Tests completed JVM Fork 3; total tests: 10; classes: 1
Tests completed JVM Fork 4; total tests: 40; classes: 4
Tests completed JVM Fork 1; total tests: 50; classes: 5{quote}
The distribution is also random, results may vary between maven runs:
mvn -DforkCount=4
{quote}Tests completed JVM Fork 4; total tests: 0; classes: 0
Tests completed JVM Fork 2; total tests: 10; classes: 1
Tests completed JVM Fork 1; total tests: 30; classes: 3
Tests completed JVM Fork 3; total tests: 60; classes: 6{quote}
> Unbalanced number of test executions in forks (forkCount>1) results in no
> performance gain for jupiter/JUnit5 tests
> --
[jira] [Updated] (SUREFIRE-1760) Unbalanced number of test executions in forks (forkCount>1) results in no performance gain for jupiter/JUnit5 tests
[
https://issues.apache.org/jira/browse/SUREFIRE-1760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vlad Skarzhevskyy updated SUREFIRE-1760:
Affects Version/s: 2.22.1
2.22.2
3.0.0-M4
> Unbalanced number of test executions in forks (forkCount>1) results in no
> performance gain for jupiter/JUnit5 tests
> ---
>
> Key: SUREFIRE-1760
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1760
> Project: Maven Surefire
> Issue Type: Bug
> Components: JUnit 5.x support
>Affects Versions: 2.22.1, 2.22.2, 3.0.0-M4
>Reporter: Vlad Skarzhevskyy
>Priority: Major
>
> Running JUnit5 tests using maven-surefire-plugin with
> true e.g. mvn -DforkCount=8
> Results: number of tests in each fork is significantly unbalanced, *+some
> forks do not get tests at all+*..
> The end results is that on CI server the total test execution will take as
> long as longest fork and only 50% of the available resources are used.
> In our case we observed that our 3000 integration tests after migration to
> junit5 take 30 minutes insteads of 18 minutes as it was with junit 4.
> The balance is restored when running with reuseForks=false but this will
> cause additional overhead for complex integrations tests
> e.g. tests requiring additional setup , classpath scanning and so on..
> The results are similar with maven-surefire-plugin: 2.22.1, 2.22.2, 3.0.0-M4
> Maven 3.6.3 , openjdk version "1.8.0_242" on Linux
>
> BTW If junit-vintage-engine is used the same results observed for JUnit3 and
> JUnit4 tests.
>
> Consider example of 100 tests (10 classes 10 tests in each)
>
> [https://github.com/skarzhevskyy/range-junit/tree/master/range-junit5-surefire-fork]
>
> When running mvn -DforkCount=8 with extension that prints the number of
> tests executed in each fork getting following:
> {quote}Tests completed JVM Fork 8; total tests: 0; classes: 0
> Tests completed JVM Fork 4; total tests: 0; classes: 0
> Tests completed JVM Fork 1; total tests: 0; classes: 0
> Tests completed JVM Fork 6; total tests: 0; classes: 0
> Tests completed JVM Fork 3; total tests: 0; classes: 0
> Tests completed JVM Fork 2; total tests: 0; classes: 0
> Tests completed JVM Fork 7; total tests: 30; classes: 3
> Tests completed JVM Fork 5; total tests: 70; classes: 7
> {quote}
>
> mvn -DforkCount=4
> {quote}Tests completed JVM Fork 2; total tests: 0; classes: 0
> Tests completed JVM Fork 3; total tests: 10; classes: 1
> Tests completed JVM Fork 4; total tests: 40; classes: 4
> Tests completed JVM Fork 1; total tests: 50; classes: 5
> {quote}
>
> The distribution is also random, results may vary between maven runs:
> mvn -DforkCount=4
> {quote}Tests completed JVM Fork 4; total tests: 0; classes: 0
> Tests completed JVM Fork 2; total tests: 10; classes: 1
> Tests completed JVM Fork 1; total tests: 30; classes: 3
> Tests completed JVM Fork 3; total tests: 60; classes: 6
> {quote}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] Commented: (MJAR-139) New option to avoid empty jar creation
[ http://jira.codehaus.org/browse/MJAR-139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=241332#action_241332 ] Vlad Skarzhevskyy commented on MJAR-139: There are 'skip' Parameter for jar:test-jar goal. Would be nice to have the same for jar:jar goal. And not create main jar at all. Obviously pom test-jar would make more sense. My usage example is a creation of common tests modules. The tests are executed in different poms configured with different database bindings. > New option to avoid empty jar creation > -- > > Key: MJAR-139 > URL: http://jira.codehaus.org/browse/MJAR-139 > Project: Maven 2.x Jar Plugin > Issue Type: Improvement >Affects Versions: 2.3.1 >Reporter: Roman Ivanov > > Usage of "test-jar" is beneficial for all project, as all of them have tests. > > org.apache.maven.plugins > maven-jar-plugin > 2.3.1 > > > > test-jar > > > > > Pom artifacts and some jar artifacts does not have test and will never have > them. > In logs we have: "[WARNING] JAR will be empty - no content was marked for > inclusion!" > and empty and useless artifacts are created, deployed , ... > It will be convenient to have an plugin option to define whether skip empty > jar creation and warning or generate jar with warning in log. Does it make > sense ? > By default option will be FALSE, to comply with previous behavior. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (MASSEMBLY-768) JarInputStream unable to find manifest created by version 2.5.4
Vlad Skarzhevskyy created MASSEMBLY-768:
---
Summary: JarInputStream unable to find manifest created by
version 2.5.4
Key: MASSEMBLY-768
URL: https://issues.apache.org/jira/browse/MASSEMBLY-768
Project: Maven Assembly Plugin
Issue Type: Bug
Affects Versions: 2.5.4
Environment: windows 64 bit, java 8. maven 3.3..3
Reporter: Vlad Skarzhevskyy
The problem is non trivial to reproduce. Changing back to version 2.5.3
resolves the problem.
On some computers plugin creates a jar file with manifest unreadable by java.
JarInputStream
see comments in JarInputStream(InputStream in, boolean verify)
java expects manifest to be "either the first or the second entry in archive."
looking at the gnerated jar using winrar generate report i see that in broken
files MANIFEST.MF is not in right place.
In example below it is third place.
{noformat}
# Archive D:\sample-java\target\sample-bad.jar
2015-05-15 20:19FolderFolder META-INF
2015-05-15 20:19FolderFolder META-INF\lib
2015-05-15 20:19 274 203 META-INF\MANIFEST.MF
2015-05-14 01:43 10106 8342
META-INF\lib\mco2-sample-java-2.6.0-SNAPSHOT.jar
2015-03-04 15:46 8262 7790 mco2-sample-java.mco.png
2015-03-04 15:46 10400 1564 mco2-sample-java.mco.xml
#
# Total SizePacked Files
#29042 17899 6
{noformat}
Please let me know if you need additional info. Or a complete test project.
My assembly descriptor and partial pom with configuration will be attached
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MASSEMBLY-768) JarInputStream unable to find manifest created by version 2.5.4
[
https://issues.apache.org/jira/browse/MASSEMBLY-768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vlad Skarzhevskyy updated MASSEMBLY-768:
Attachment: pom.xml
mco.xml
> JarInputStream unable to find manifest created by version 2.5.4
>
>
> Key: MASSEMBLY-768
> URL: https://issues.apache.org/jira/browse/MASSEMBLY-768
> Project: Maven Assembly Plugin
> Issue Type: Bug
>Affects Versions: 2.5.4
> Environment: windows 64 bit, java 8. maven 3.3..3
>Reporter: Vlad Skarzhevskyy
> Attachments: mco.xml, pom.xml
>
>
> The problem is non trivial to reproduce. Changing back to version 2.5.3
> resolves the problem.
> On some computers plugin creates a jar file with manifest unreadable by java.
> JarInputStream
> see comments in JarInputStream(InputStream in, boolean verify)
> java expects manifest to be "either the first or the second entry in archive."
> looking at the gnerated jar using winrar generate report i see that in broken
> files MANIFEST.MF is not in right place.
> In example below it is third place.
> {noformat}
> # Archive D:\sample-java\target\sample-bad.jar
> 2015-05-15 20:19FolderFolder META-INF
> 2015-05-15 20:19FolderFolder META-INF\lib
> 2015-05-15 20:19 274 203 META-INF\MANIFEST.MF
> 2015-05-14 01:43 10106 8342
> META-INF\lib\mco2-sample-java-2.6.0-SNAPSHOT.jar
> 2015-03-04 15:46 8262 7790 mco2-sample-java.mco.png
> 2015-03-04 15:46 10400 1564 mco2-sample-java.mco.xml
> #
> # Total SizePacked Files
> #29042 17899 6
> {noformat}
> Please let me know if you need additional info. Or a complete test project.
> My assembly descriptor and partial pom with configuration will be attached
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] Created: (MAVENUPLOAD-2305) Uploading proguard 4.3 to The Central Repository
Uploading proguard 4.3 to The Central Repository Key: MAVENUPLOAD-2305 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2305 Project: Maven Upload Requests Issue Type: Wish Reporter: Vlad Skarzhevskyy Please Upload the latest version to Repository. The last version (posted by me) in repository is 4.2 http://pyx4j.com/downloads/proguard-4.3-bundle.jar http://proguard.sourceforge.net/ ProGuard is a free Java class file shrinker, optimizer, and obfuscator. It removes unused classes, fields, methods, and attributes. It then optimizes the bytecode. It then renames the remaining classes, fields, and methods using short meaningless names. Finally, it preverifies the processed code for Java 6 or for Java Micro Edition. Changes in 4.3: - Added class merging. - Added static single assignment analysis. - Added support for annotation and enumeration class types in configuration. - Refined shrinking of fields in case of unusual -keepclassmembers options. - Added simplification of tail recursion calls. - Added new peephole optimizations. - Fixed optimization of unused variable initializations causing negative stack sizes. - Fixed optimization of unusual initialization code causing NullPointerExceptions. - Fixed optimization of half-used long and double parameters. - Fixed processing of complex generics signatures. - Working around suspected java compiler bug with parameter annotations on constructors of non-static inner classes. - Fixed obfuscation of classes with inner classes whose names are preserved. - Fixed access of protected methods in repackaged classes. - Added options -classobfuscationdictionary and -packageobfuscationdictionary. - Adapting more types of resource file names based on obfuscation. - Extended warnings about incorrect dependencies. - Added start-up scripts and build scripts. - Updated documentation and examples -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (JXR-70) Remove Link to non exisitng javadocs, package access level classes
Remove Link to non exisitng javadocs, package access level classes
--
Key: JXR-70
URL: http://jira.codehaus.org/browse/JXR-70
Project: Maven JXR
Issue Type: Improvement
Components: maven2 jxr plugin
Affects Versions: 2.1
Environment: maven2
Reporter: Vlad Skarzhevskyy
Link "View Javadoc" created for package access level classes.
This creates many "404 Not Found" on webserver and hides the real problems on
website...
Since maven-javadoc-plugin have it configurable:
http://maven.apache.org/plugins/maven-javadoc-plugin/javadoc-mojo.html#show
Would be nice to have this as configuration in maven-jxr-plugin.
linkJavadocShow or linkJavadocAccessLevel
As well linkJavadocExcludePackageNames may be easy to add for complete
compatibility with javadoc-plugin excludePackageNames
Alternative would be to verify if target file exists in directory ${javadocDir}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Reopened: (SUREFIRE-318) Fails to run build on Windows Server 2003
[ http://jira.codehaus.org/browse/SUREFIRE-318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vlad Skarzhevskyy reopened SUREFIRE-318: Build on Windows Server 2003 failed again! build log --- Downloading: http://people.apache.org/repo/m2-snapshot-repository/org/apache/maven/surefire/surefire/2.3.1-SNAPSHOT/surefire-2.3.1-20070606.164150-5.pom Downloading: http://people.apache.org/repo/m2-snapshot-repository/org/apache/maven/plugins/maven-surefire-plugin/2.3.1-SNAPSHOT/maven-surefire-plugin-2.3.1-20070606.164150-5.jar [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] There are test failures. [INFO] build log --- May be the the problem is because I don't have any tests defined in a module But it works fine on WinXP I removed the empty directories for test cases and the module build compleated. but now next module fails that real has Unit tests. C:\build\work\pyx4j-gwt\log4gwt>m2 -e + Error stacktraces are turned on. [INFO] Scanning for projects... [INFO] [INFO] Building pyx4j-log4gwt [INFO]task-segment: [install] [INFO] [INFO] [resources:resources] [INFO] Using default encoding to copy filtered resources. [INFO] [compiler:compile] [INFO] Nothing to compile - all classes are up to date [INFO] [resources:testResources] [INFO] Using default encoding to copy filtered resources. [INFO] [compiler:testCompile] [INFO] Nothing to compile - all classes are up to date [INFO] [surefire:test] [INFO] Surefire report directory: C:\build\work\pyx4j-gwt\log4gwt\target\surefire-reports [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] There are test failures. [INFO] [INFO] Trace org.apache.maven.BuildFailureException: There are test failures. at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:560) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:48 0) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:459) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.jav a:311) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125) at org.apache.maven.cli.MavenCli.main(MavenCli.java:272) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) 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) Caused by: org.apache.maven.plugin.MojoFailureException: There are test failures. at org.apache.maven.plugin.surefire.SurefirePlugin.execute(SurefirePlugin.java:425) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:443) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539) ... 16 more [INFO] [INFO] Total time: 2 seconds [INFO] Finished at: Wed Jul 25 14:38:39 EDT 2007 [INFO] Final Memory: 5M/178M [INFO] C:\build\work\pyx4j-gwt\log4gwt> Maven version: 2.0.6 > Fails to run build on Windows Server 2003 > - > > Key: SUREFIRE-318 > URL: http://jira.codehaus.org/browse/SUREFIRE-318 > Project: Maven Surefire > Issue Type: Bug >Affects Versions: 2.3 > Environment: Maven 2.0.5 or 2.0.6 , Windows Server 2003, Java 1.5 or > 1.6 >Reporter: Vlad Skarzhevskyy >
[jira] Created: (MAVENUPLOAD-1689) Uploading pyx4j 1.0.1 to The Central Repository
Uploading pyx4j 1.0.1 to The Central Repository --- Key: MAVENUPLOAD-1689 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1689 Project: maven-upload-requests Issue Type: Task Reporter: Vlad Skarzhevskyy Attachments: m2-sync-com.pyx4j.sh http://pyx4j.com/ The collection of libs for maven-plugins used in other projects we already published of planning to publish next. * jour.sourceforge.net Jour a bytecode instrumentation library. (depends on pyx4j libs) to be published next) * pyx4me.com J2ME JUnit base test framework and a collection of build tools for maven2 & J2ME. (Needs jour to cldcUnit) * microemu.org Java implementation of J2ME in J2SE. rsync created. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MAVENUPLOAD-1690) Upload Jour 2.0.0 to The Central Repository
Upload Jour 2.0.0 to The Central Repository --- Key: MAVENUPLOAD-1690 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1690 Project: maven-upload-requests Issue Type: Task Reporter: Vlad Skarzhevskyy Attachments: m2-sync-net.sf.jour.sh The Jour library is an open source suite of java bytecode instrumentation base on Javassist. Contains jour-maven-plugin and instrumentation wrapper around Javassist Jour used by this projects: * pyx4me.com J2ME JUnit base test framework and a collection of build tools for maven2 & J2ME. * microemu.org Java implementation of J2ME in J2SE. rsync created. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MAVENUPLOAD-1691) Uploading BlueCove 2.0.1 to repository
Uploading BlueCove 2.0.1 to repository --- Key: MAVENUPLOAD-1691 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1691 Project: maven-upload-requests Issue Type: Task Reporter: Vlad Skarzhevskyy New version 2.0.1 * L2CAP imlementation, Only on WIDCOMM stack * Use TCK for JSR 82 for tests, fixed major incompatibility problems * Full OBEX over RFCOMM and TCP -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MAVENUPLOAD-1709) Uploading proguard 3.10.1 to The Central Repository
Uploading proguard 3.10.1 to The Central Repository --- Key: MAVENUPLOAD-1709 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1709 Project: maven-upload-requests Issue Type: Task Reporter: Vlad Skarzhevskyy Please Upload the latest version to Repository. The last version (posted by me) in repository is 3.9 http://pyx4j.com/downloads/proguard-3.10.1-bundle.jar http://proguard.sourceforge.net/ ProGuard is a free Java class file shrinker, optimizer, and obfuscator. It removes unused classes, fields, methods, and attributes. It then optimizes the bytecode. It then renames the remaining classes, fields, and methods using short meaningless names. Version 3.10 - Now handling mixed-case input class names when -dontusemixedcaseclassnames is specified. - Fixed optimization of synchronization on classes, as compiled by Eclipse and Jikes. - Fixed optimization of switch statements with unreachable cases. - Avoiding merging subsequent identically named files. - Updated documentation and examples. Version 3.10.1 fixes an optimization bug that was introduced in 3.10 (processing the creation of objects that are not actually assigned or used). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MAVENUPLOAD-1754) Uploading proguard 4.0 to The Central Repository
Uploading proguard 4.0 to The Central Repository Key: MAVENUPLOAD-1754 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1754 Project: maven-upload-requests Issue Type: Task Reporter: Vlad Skarzhevskyy Please Upload the latest version to Repository. The last version (posted by me) in repository is 3.10 http://pyx4j.com/downloads/proguard-4.0-bundle.jar http://proguard.sourceforge.net/ ProGuard is a free Java class file shrinker, optimizer, and obfuscator. It removes unused classes, fields, methods, and attributes. It then optimizes the bytecode. It then renames the remaining classes, fields, and methods using short meaningless names. Version 4.0 * Added preverifier for Java 6 and Java Micro Edition, with new options -microedition and -dontpreverify. * Added new option -target to modify java version of processed class files. * Made -keep options more orthogonal and flexible, with option modifiers allowshrinking, allowoptimization, and allowobfuscation. * Added new wildcards for class member descriptors: "***", matching any type, and "...", matching any number of arguments. * Added support for configuration by means of annotations. * Improved shrinking of unused annotations. * Added check on modification times of input and output, to avoid unnecessary processing, with new option -forceprocessing. * Added new options -flattenpackagehierarchy and -repackageclasses (replacing -defaultpackage) to control obfuscation of package names. * Added new options -adaptresourcefilenames and -adaptresourcefilecontents, with file filters, to update resource files corresponding to obfuscated class names. * Added detection of dynamically accessed fields and methods. * Now treating Exceptions attributes as optional. * Now respecting naming rule for nested class names (EnclosingClass$InnerClass) in obfuscation step, if InnerClasses attributes or EnclosingMethod attributes are being kept. * Added new inter-procedural optimizations: method inlining and propagation of constant fields, constant arguments, and constant return values. * Added optimized local variable allocation. * Added over 250 new peephole optimizations. * Improved making classes and class members public or protected. * Now printing notes on suspiciously unkept classes in parameters of specified methods. * Now printing notes for class names that don't seem to be fully qualified. * Added support for uppercase filename extensions. * Added tool tips to the GUI. * Rewritten class file I/O code. * Updated documentation and examples. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MAVENUPLOAD-2105) Uploading proguard 4.2 to The Central Repository
Uploading proguard 4.2 to The Central Repository Key: MAVENUPLOAD-2105 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2105 Project: Maven Upload Requests Issue Type: Task Reporter: Vlad Skarzhevskyy Please Upload the latest version to Repository. The last version (posted by me) in repository is 4.1 http://pyx4j.com/downloads/proguard-4.2-bundle.jar http://proguard.sourceforge.net/ ProGuard is a free Java class file shrinker, optimizer, and obfuscator. It removes unused classes, fields, methods, and attributes. It then optimizes the bytecode. It then renames the remaining classes, fields, and methods using short meaningless names. Finally, it preverifies the processed code for Java 6 or for Java Micro Edition. Changes in 4.2: * Refined data flow analysis in optimization step. * Fixed handling of exceptions when inlining subroutines. * Fixed inlining of incompatible code constructs between different java versions. * Fixed computation of local variable frame size. * Fixed optimization of infinite loops. * Fixed optimization of subroutine invocations. * Fixed optimization of floating point remainder computations. * Fixed removal of unused parameters in method descriptors containing arrays of longs or doubles. * Added undocumented java system properties maximum.inlined.code.length (default is 8) and maximum.resulting.code.length (defaults are 8000 for JSE and 2000 for JME), for expert users who read release notes. * Fixed processing of generic types in Signature attributes in shrinking and optimization steps. * Fixed processing of inner class names in Signature attributes in obfuscation step. * Improved adapting resource file names following obfuscated class names. * Fixed interpretation of package names in GUI. * Fixed default settings for Xlets in GUI. * Updated documentation and examples. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MAVENUPLOAD-2108) Uploading antenna 1.0.2 to The Central Repository
Uploading antenna 1.0.2 to The Central Repository - Key: MAVENUPLOAD-2108 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2108 Project: Maven Upload Requests Issue Type: Task Reporter: Vlad Skarzhevskyy Please Upload the latest version to Repository. The last version (posted by me) in repository is 0.9.14 The antenna project provides a set of Ant tasks for developing J2ME/MIDP applications based on the J2ME Wireless Toolkit. Maven plugin exists (j2me-maven-plugin) to use this library in maven build. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MAVENUPLOAD-2158) Sync'ing BlueCove with repository
Sync'ing BlueCove with repository - Key: MAVENUPLOAD-2158 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2158 Project: Maven Upload Requests Issue Type: Wish Reporter: Vlad Skarzhevskyy Attachments: m2-sync-net.sf.bluecove.sh Would be nice if rsync created. "net.sf.bluecove","[EMAIL PROTECTED]::maven2-release","rsync","Vlad Skarzhevskyy","[EMAIL PROTECTED]",, This is the same as for all other projects sync'ing from this build server. (org.microemu and com.pyx4me) The directory http://www.pyx4me.com/maven2-release/net/sf/bluecove/bluecove/ already contains previously published artifacts, hope this is not a problem. The next BlueCove release would have 3 jars/modules instead of one as it used to before, so creating rsync looks like right option. The project is published on sf http://sourceforge.net/projects/bluecove/ so we are going to keep old groupId net.sf.bluecove -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MAVENUPLOAD-1442) Uploading proguard 3.8 to The Central Repository
Uploading proguard 3.8 to The Central Repository Key: MAVENUPLOAD-1442 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1442 Project: maven-upload-requests Issue Type: Task Reporter: Vlad Skarzhevskyy Please Upload the latest version to Repository. The last version (posted by me) in repository is 3.7 http://pyx4j.com/downloads/proguard-3.8-bundle.jar http://proguard.sourceforge.net/ ProGuard is a free Java class file shrinker, optimizer, and obfuscator. It removes unused classes, fields, methods, and attributes. It then optimizes the bytecode. It then renames the remaining classes, fields, and methods using short meaningless names. Version 3.8 # Fixed optimization of parameters used as local variables. # Fixed obfuscation with conflicting class member names. # Fixed incremental obfuscation with incomplete mapping file for library jars. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (SUREFIRE-318) Fails to run build on Windows Server 2003
Fails to run build on Windows Server 2003 - Key: SUREFIRE-318 URL: http://jira.codehaus.org/browse/SUREFIRE-318 Project: Maven Surefire Issue Type: Bug Affects Versions: 2.3 Environment: Maven 2.0.5 or 2.0.6 , Windows Server 2003, Java 1.5 or 1.6 Reporter: Vlad Skarzhevskyy Attachments: build-log.txt After Upgrade to Surefire 2.3 our build server fails to run tests on any project. Get the message: [ERROR] BUILD FAILURE [INFO] [INFO] There are test failures. [INFO] All works fine on Linux, WinXP and Win2000. But when I try to build on any Windows Server 2003 build will fail. See the log mvn -X test > build-log.txt -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MAVENUPLOAD-1493) Uploading pyx4me 2.0.1 to The Central Repository
Uploading pyx4me 2.0.1 to The Central Repository Key: MAVENUPLOAD-1493 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1493 Project: maven-upload-requests Issue Type: Task Reporter: Vlad Skarzhevskyy The collection of maven-plugins and Archetype used develop applications for the Java Micro Edition Platform Upload has 3 parent poms to be loaded first. http://www.pyx4j.com/downloads/pyx4me-2.0.1/pyx4me-parent-2.0.1-bundle.jar http://www.pyx4j.com/downloads/pyx4me-2.0.1/pyx4me-maven-plugins-parent-2.0.1-bundle.jar http://www.pyx4j.com/downloads/pyx4me-2.0.1/j2me-maven-plugin-2.0.1-bundle.jar http://www.pyx4j.com/downloads/pyx4me-2.0.1/proguard-maven-plugin-2.0.1-bundle.jar http://www.pyx4j.com/downloads/pyx4me-2.0.1/pyx4me-archetypes-parent-2.0.1-bundle.jar http://www.pyx4j.com/downloads/pyx4me-2.0.1/j2me-simple-2.0.1-bundle.jar -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Reopened: (MAVENUPLOAD-1493) Uploading pyx4me 2.0.1 to The Central Repository
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vlad Skarzhevskyy reopened MAVENUPLOAD-1493: Next time: I will create repository. No problem. I'm going to make release microemulator soon. The problem I have now: How do I update maven-metadata.xml. Is it loaded from repository for sync? Now tag is missing in plugins e.g.: com/pyx4me/proguard-maven-plugin/maven-metadata.xml This does not allow me to use plugin withour refferencing its version in other projects. > Uploading pyx4me 2.0.1 to The Central Repository > > > Key: MAVENUPLOAD-1493 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1493 > Project: maven-upload-requests > Issue Type: Task >Reporter: Vlad Skarzhevskyy >Assignee: Carlos Sanchez > > The collection of maven-plugins and Archetype used develop applications for > the Java Micro Edition Platform > Upload has 3 parent poms to be loaded first. > http://www.pyx4j.com/downloads/pyx4me-2.0.1/pyx4me-parent-2.0.1-bundle.jar > http://www.pyx4j.com/downloads/pyx4me-2.0.1/pyx4me-maven-plugins-parent-2.0.1-bundle.jar > http://www.pyx4j.com/downloads/pyx4me-2.0.1/j2me-maven-plugin-2.0.1-bundle.jar > http://www.pyx4j.com/downloads/pyx4me-2.0.1/proguard-maven-plugin-2.0.1-bundle.jar > http://www.pyx4j.com/downloads/pyx4me-2.0.1/pyx4me-archetypes-parent-2.0.1-bundle.jar > http://www.pyx4j.com/downloads/pyx4me-2.0.1/j2me-simple-2.0.1-bundle.jar -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MAVENUPLOAD-1493) Uploading pyx4me 2.0.1 to The Central Repository
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_94134 ] Vlad Skarzhevskyy commented on MAVENUPLOAD-1493: I will create repository and let you know. Don't spend time on this for now. > Uploading pyx4me 2.0.1 to The Central Repository > > > Key: MAVENUPLOAD-1493 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1493 > Project: maven-upload-requests > Issue Type: Task >Reporter: Vlad Skarzhevskyy >Assignee: Carlos Sanchez > > The collection of maven-plugins and Archetype used develop applications for > the Java Micro Edition Platform > Upload has 3 parent poms to be loaded first. > http://www.pyx4j.com/downloads/pyx4me-2.0.1/pyx4me-parent-2.0.1-bundle.jar > http://www.pyx4j.com/downloads/pyx4me-2.0.1/pyx4me-maven-plugins-parent-2.0.1-bundle.jar > http://www.pyx4j.com/downloads/pyx4me-2.0.1/j2me-maven-plugin-2.0.1-bundle.jar > http://www.pyx4j.com/downloads/pyx4me-2.0.1/proguard-maven-plugin-2.0.1-bundle.jar > http://www.pyx4j.com/downloads/pyx4me-2.0.1/pyx4me-archetypes-parent-2.0.1-bundle.jar > http://www.pyx4j.com/downloads/pyx4me-2.0.1/j2me-simple-2.0.1-bundle.jar -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MAVENUPLOAD-1493) Uploading pyx4me 2.0.1 to The Central Repository
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vlad Skarzhevskyy updated MAVENUPLOAD-1493: --- Attachment: m2-sync-com.pyx4me.sh Created release directory web access http://pyx4me.com/maven2-release/ rsync script created --- Carlos, for another project org/microemu/ published in the same directory should I create a new script ? > Uploading pyx4me 2.0.1 to The Central Repository > > > Key: MAVENUPLOAD-1493 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1493 > Project: maven-upload-requests > Issue Type: Task >Reporter: Vlad Skarzhevskyy >Assignee: Carlos Sanchez > Attachments: m2-sync-com.pyx4me.sh > > > The collection of maven-plugins and Archetype used develop applications for > the Java Micro Edition Platform > Upload has 3 parent poms to be loaded first. > http://www.pyx4j.com/downloads/pyx4me-2.0.1/pyx4me-parent-2.0.1-bundle.jar > http://www.pyx4j.com/downloads/pyx4me-2.0.1/pyx4me-maven-plugins-parent-2.0.1-bundle.jar > http://www.pyx4j.com/downloads/pyx4me-2.0.1/j2me-maven-plugin-2.0.1-bundle.jar > http://www.pyx4j.com/downloads/pyx4me-2.0.1/proguard-maven-plugin-2.0.1-bundle.jar > http://www.pyx4j.com/downloads/pyx4me-2.0.1/pyx4me-archetypes-parent-2.0.1-bundle.jar > http://www.pyx4j.com/downloads/pyx4me-2.0.1/j2me-simple-2.0.1-bundle.jar -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MAVENUPLOAD-1519) Uploading MicroEmulator 2.0.1 to The Central Repository
Uploading MicroEmulator 2.0.1 to The Central Repository --- Key: MAVENUPLOAD-1519 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1519 Project: maven-upload-requests Issue Type: Task Reporter: Vlad Skarzhevskyy Attachments: m2-sync-org.microemu.sh MicroEmulator is a pure Java implementation of J2ME in J2SE. MicroEmulator is licensed under LGP. rsync script created see Attachment. Carlos Will this script run automatically when I put another version to my repository? Is how can I test the local version before publishing it in Central Repository? Just stop rsync daemon? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MAVENUPLOAD-1534) uploading bluecove-1.2.3 to The Central Repository
uploading bluecove-1.2.3 to The Central Repository -- Key: MAVENUPLOAD-1534 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1534 Project: maven-upload-requests Issue Type: Task Reporter: Vlad Skarzhevskyy BlueCove is a LGPL licensed JSR-82 implementation that currently interfaces with the Microsoft Bluetooth stack -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SUREFIRE-318) Fails to run build on Windows Server 2003
[ http://jira.codehaus.org/browse/SUREFIRE-318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_97002 ] Vlad Skarzhevskyy commented on SUREFIRE-318: I added http://people.apache.org/repo/m2-snapshot-repository to my project. Changed: maven-surefire-plugin 2.3.1-SNAPSHOT Now it does not run even Windows XP. [INFO] [surefire:test] [INFO] Surefire report directory: D:\devGwt\pyx4j\commons\target\surefire-report s [INFO] Building jar: D:\tmp\usr\vlads\surefirebooter23854.jar java.lang.NoClassDefFoundError: org/apache/maven/surefire/booter/SurefireBooter Exception in thread "main" [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] There are test failures. Maven version: 2.0.5 This file was downloaded maven-surefire-plugin-2.3.1-20070524.103536-2.jar > Fails to run build on Windows Server 2003 > - > > Key: SUREFIRE-318 > URL: http://jira.codehaus.org/browse/SUREFIRE-318 > Project: Maven Surefire > Issue Type: Bug >Affects Versions: 2.3 > Environment: Maven 2.0.5 or 2.0.6 , Windows Server 2003, Java 1.5 or > 1.6 >Reporter: Vlad Skarzhevskyy > Fix For: 2.3.1 > > Attachments: build-log.txt > > > After Upgrade to Surefire 2.3 our build server fails to run tests on any > project. > Get the message: > [ERROR] BUILD FAILURE > [INFO] > > [INFO] There are test failures. > [INFO] > > All works fine on Linux, WinXP and Win2000. > But when I try to build on any Windows Server 2003 build will fail. > See the log > mvn -X test > build-log.txt -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SUREFIRE-318) Fails to run build on Windows Server 2003
[ http://jira.codehaus.org/browse/SUREFIRE-318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_97041 ] Vlad Skarzhevskyy commented on SUREFIRE-318: Works fine on XP and Win server 2003 Thanks! > Fails to run build on Windows Server 2003 > - > > Key: SUREFIRE-318 > URL: http://jira.codehaus.org/browse/SUREFIRE-318 > Project: Maven Surefire > Issue Type: Bug >Affects Versions: 2.3 > Environment: Maven 2.0.5 or 2.0.6 , Windows Server 2003, Java 1.5 or > 1.6 >Reporter: Vlad Skarzhevskyy > Fix For: 2.3.1 > > Attachments: build-log.txt > > > After Upgrade to Surefire 2.3 our build server fails to run tests on any > project. > Get the message: > [ERROR] BUILD FAILURE > [INFO] > > [INFO] There are test failures. > [INFO] > > All works fine on Linux, WinXP and Win2000. > But when I try to build on any Windows Server 2003 build will fail. > See the log > mvn -X test > build-log.txt -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MAVENUPLOAD-1625) BlueCove 2.0.0 release
BlueCove 2.0.0 release -- Key: MAVENUPLOAD-1625 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1625 Project: maven-upload-requests Issue Type: Task Reporter: Vlad Skarzhevskyy BlueCove is a fantastic piece of software for JSR-82. Please upload! :) Now has WIDCOMM and BlueSoleil Bluetooth stack in addition to Microsoft -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MAVENUPLOAD-1626) Uploading proguard 3.9 to The Central Repository
Uploading proguard 3.9 to The Central Repository Key: MAVENUPLOAD-1626 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1626 Project: maven-upload-requests Issue Type: Task Reporter: Vlad Skarzhevskyy Please Upload the latest version to Repository. The last version (posted by me) in repository is 3.8 http://pyx4j.com/downloads/proguard-3.9-bundle.jar http://proguard.sourceforge.net/ ProGuard is a free Java class file shrinker, optimizer, and obfuscator. It removes unused classes, fields, methods, and attributes. It then optimizes the bytecode. It then renames the remaining classes, fields, and methods using short meaningless names. Version 3.9 * Fixed processing of .class constructs in Java 6. * Fixed repeated processing of .class constructs. * Fixed possible division by 0 in optimization step. * Fixed handling of variable instructions with variable indices larger than 255. * Updated documentation and examples. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MAVENUPLOAD-1627) Uploading antenna 0.9.14 to The Central Repository
Uploading antenna 0.9.14 to The Central Repository -- Key: MAVENUPLOAD-1627 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1627 Project: maven-upload-requests Issue Type: Task Reporter: Vlad Skarzhevskyy The project provides a set of Ant tasks for developing J2ME/MIDP applications based on the J2ME Wireless Toolkit. The new tasks allow for compilation, preverification, packaging, and obfuscation of a MIDlet suite as well as for making a PalmOS PRC file. Explanation for upload. In my case antenna is used by pyx4me.com j2me-maven-plugin that is alredy in Repository. I contacted the developers and got no reply. They are buzy or ... But definitly they are not against and "GNU LESSER GENERAL PUBLIC LICENSE" allow! The older version of antenna is avalable in berlios.de maven Repository. net.sf.antenna antenna -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MAVENUPLOAD-1864) Uploading proguard 4.1 to The Central Repository
Uploading proguard 4.1 to The Central Repository Key: MAVENUPLOAD-1864 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1864 Project: maven-upload-requests Issue Type: Task Reporter: Vlad Skarzhevskyy Please Upload the latest version to Repository. The last version (posted by me) in repository is 4.0.1 http://pyx4j.com/downloads/proguard-4.1-bundle.jar http://proguard.sourceforge.net/ ProGuard is a free Java class file shrinker, optimizer, and obfuscator. It removes unused classes, fields, methods, and attributes. It then optimizes the bytecode. It then renames the remaining classes, fields, and methods using short meaningless names. Changes in 4.1: - Fixed shrinking of default annotation element values. - Fixed optimization of invocations of methods in same class that are accessed through extensions. - Fixed optimization of invocations of synchronized methods without other side-effects. - Fixed optimization of some non-returning subroutines. - Fixed handling of local variable debug information when inlining methods. - Avoiding StackOverflowErrors during optimization of complex methods. - Fixed obfuscation of potentially ambiguous non-primitive constants in interfaces. - Fixed preverification of some code constructs involving String, Class, and exception types. - The Ant task now allows empty and elements. - Updated documentation and examples. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MAVENUPLOAD-1885) Uploading BlueCove 2.0.2 to repository
Uploading BlueCove 2.0.2 to repository -- Key: MAVENUPLOAD-1885 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1885 Project: maven-upload-requests Issue Type: Task Reporter: Vlad Skarzhevskyy New in version 2.0.2 * Support for Mac OSX -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MSITE-288) xdoc translation, tag is removed from generated html
xdoc translation, tag is removed from generated html - Key: MSITE-288 URL: http://jira.codehaus.org/browse/MSITE-288 Project: Maven 2.x Site Plugin Issue Type: Bug Components: doxia integration Affects Versions: 2.0-beta-6 Environment: maven 2.0.7, Java any (: 1.5.0_12) the same on Windows XP and Linux Reporter: Vlad Skarzhevskyy xdoc translation to html is broken tag is removed from generated html We have this fragment in the code: --- -- translates to html: --- --- tag is removed from generated html Project: http://snapshot.microemu.org/ Solution we have now is to rollback maven-site-plugin to 2.0-beta-5 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MASSEMBLY-291) attach the resulting assembly not working as expected
attach the resulting assembly not working as expected - Key: MASSEMBLY-291 URL: http://jira.codehaus.org/browse/MASSEMBLY-291 Project: Maven 2.x Assembly Plugin Issue Type: Bug Affects Versions: 2.2-beta-2 Environment: Maven version: 2.0.8 Java version: 1.5.0_14 OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows" Reporter: Vlad Skarzhevskyy After changing to 2.2-beta-2 attach is not working in our project. This is configuration used: project: pom maven-assembly-plugin: package single true false The idea is to replace main artifact jar with created jar. packaging pom has been selected base on example form the site. May be this is wrong but used to work in version 2.1. Full Project here: https://microemulator.svn.sourceforge.net/svnroot/microemulator/branches/microemulator_2_0_2/microemulator PS We also have second sources assembly in the same pom.xml This assembly is installed to local repository! -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MAVENUPLOAD-1327) uploading bluecove-1.2.1 to The Central Repository
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1327?page=comments#action_85537 ] Vlad Skarzhevskyy commented on MAVENUPLOAD-1327: groupId Updated to net.sf.bluecove bluecove-1.2.1-bundle.jar updated. > uploading bluecove-1.2.1 to The Central Repository > --- > > Key: MAVENUPLOAD-1327 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1327 > Project: maven-upload-requests > Issue Type: Task >Reporter: Vlad Skarzhevskyy > > http://pyx4j.com/downloads/bluecove-1.2.1-bundle.jar > BlueCove is a LGPL licensed JSR-82 implementation that currently interfaces > with the Microsoft Bluetooth stack -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MAVENUPLOAD-1332) uploading jfig-1.5.1 to The Central Repository
uploading jfig-1.5.1 to The Central Repository -- Key: MAVENUPLOAD-1332 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1332 Project: maven-upload-requests Issue Type: Task Reporter: Vlad Skarzhevskyy http://pyx4j.com/downloads/jfig-1.5.1-bundle.jar A Configuration utility that provides simple, flexible and powerful functionality for managing one or more configurations in a java environment. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MAVENUPLOAD-1351) Uploading MicroEmulator 2.0.0 to The Central Repository
Uploading MicroEmulator 2.0.0 to The Central Repository Key: MAVENUPLOAD-1351 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1351 Project: maven-upload-requests Issue Type: Task Reporter: Vlad Skarzhevskyy http://www.microemu.org/downloads/microemulator-app-swing-2.0.0-bundle.jar MicroEmulator is a pure Java implementation of J2ME in J2SE. MicroEmulator is licensed under LGP. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MAVENUPLOAD-1357) Uploading proguard 3.7 to The Central Repository
Uploading proguard 3.7 to The Central Repository Key: MAVENUPLOAD-1357 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1357 Project: maven-upload-requests Issue Type: Task Reporter: Vlad Skarzhevskyy Please Upload the latest version to Repository. The last version posted in repository is 3.4 http://pyx4j.com/downloads/proguard3.7-bundle.jar http://proguard.sourceforge.net/ ProGuard is a free Java class file shrinker, optimizer, and obfuscator. It removes unused classes, fields, methods, and attributes. It then optimizes the bytecode. It then renames the remaining classes, fields, and methods using short meaningless names. Version 3.7 Now accepting Java 6 class files -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MECLIPSE-229) multiproject with classifier dependency on another module
multiproject with classifier dependency on another module
-
Key: MECLIPSE-229
URL: http://jira.codehaus.org/browse/MECLIPSE-229
Project: Maven 2.x Eclipse Plugin
Issue Type: Bug
Components: multiproject
Affects Versions: 2.3, 2.2
Environment: windows, java5, multiproject
Reporter: Vlad Skarzhevskyy
I have module "microemu-injected" with artifact inject
org.microemu
microemu-injected
${version}
inject
When I generate eclipse project I got dependency on complete project not just
to its artifact.
When generating project for each module separately
And this is what I need.
But I have other project dependancy so I can't use
useProjectReferences:false
Project
https://microemulator.svn.sourceforge.net/svnroot/microemulator/trunk/microemulator
Is it posible to add filter to configuration of maven-eclipse-plugin
to trigger different behaviour for this situation.
like this:
false
microemu-injected
or
Simple :
false
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MECLIPSE-229) multiproject with classifier dependency on another module
[
http://jira.codehaus.org/browse/MECLIPSE-229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vlad Skarzhevskyy updated MECLIPSE-229:
---
Attachment: noProjectReferences.patch
suggested solution for problem
special-module1
special-module2
patch made on trunk from February 13 SVN revision 494359
https://svn.apache.org/repos/asf/maven/plugins/trunk/maven-eclipse-plugin
> multiproject with classifier dependency on another module
> -
>
> Key: MECLIPSE-229
> URL: http://jira.codehaus.org/browse/MECLIPSE-229
> Project: Maven 2.x Eclipse Plugin
> Issue Type: Bug
> Components: multiproject
>Affects Versions: 2.2, 2.3
> Environment: windows, java5, multiproject
>Reporter: Vlad Skarzhevskyy
> Attachments: noProjectReferences.patch
>
>
> I have module "microemu-injected" with artifact
> inject
>
> org.microemu
> microemu-injected
> ${version}
> inject
>
> When I generate eclipse project I got dependency on complete project not just
> to its artifact.
>
> When generating project for each module separately
> path="M2_REPO/org/microemu/microemu-injected/2.0.1-SNAPSHOT/microemu-injected-2.0.1-SNAPSHOT-inject.jar"/>
>And this is what I need.
>But I have other project dependancy so I can't use
> useProjectReferences:false
> Project
> https://microemulator.svn.sourceforge.net/svnroot/microemulator/trunk/microemulator
> Is it posible to add filter to configuration of maven-eclipse-plugin
> to trigger different behaviour for this situation.
> like this:
>
>
> false
>
> microemu-injected
>
>
>
> or
> Simple :
>
> false
>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MECLIPSE-230) Classpath entries to be marked exported
Classpath entries to be marked exported --- Key: MECLIPSE-230 URL: http://jira.codehaus.org/browse/MECLIPSE-230 Project: Maven 2.x Eclipse Plugin Issue Type: Improvement Components: dependency resolution Affects Versions: 2.1 Reporter: Vlad Skarzhevskyy Assigned To: fabrizio giustina Fix For: 2.3 Generated .classpath entries of kind "var" need to be marked exported by default so that referenced projects have visibility to them. Or provide an option to specifiy that that entries should be exported. Example: should me made... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MECLIPSE-230) Classpath entries to be marked exported
[ http://jira.codehaus.org/browse/MECLIPSE-230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_87521 ] Vlad Skarzhevskyy commented on MECLIPSE-230: Tried to clone old problem did not work well sorry. Original MECLIPSE-95 Transitive classpath entries need to be marked exported This is actual Request for feature. To have in plugin configuration with new list: artifact1 artifact2 The reason for this is creation EclipseME nature Only the exported artifacts would be added to MIDlet Suite http://eclipseme.org/docs/faq.html#addJar or http://eclipseme.org/docs/advJarFiles.html This is what I do now to create EclipseME: > Classpath entries to be marked exported > --- > > Key: MECLIPSE-230 > URL: http://jira.codehaus.org/browse/MECLIPSE-230 > Project: Maven 2.x Eclipse Plugin > Issue Type: Improvement > Components: dependency resolution >Affects Versions: 2.1 >Reporter: Vlad Skarzhevskyy > Assigned To: fabrizio giustina > Fix For: 2.3 > > > Generated .classpath entries of kind "var" need to be marked exported by > default so that referenced projects have visibility to them. Or provide an > option to specifiy that that entries should be exported. > Example: path="M2_REPO/mx4j/mx4j/3.0.1/mx4j-3.0.1.jar"/> > should me made... > path="M2_REPO/mx4j/mx4j/3.0.1/mx4j-3.0.1.jar"/> -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MASSEMBLY-188) manifestEntries are not set in resulting jar
manifestEntries are not set in resulting jar
Key: MASSEMBLY-188
URL: http://jira.codehaus.org/browse/MASSEMBLY-188
Project: Maven 2.x Assembly Plugin
Issue Type: Bug
Affects Versions: 2.1
Environment: maven 2.0.5, windows/linux
Reporter: Vlad Skarzhevskyy
archive manifestEntries are not set in resulting jar. even so the mainClass is
set properly.
assembly format is jar
Example:
true
false
assembly.xml
org.microemu.app.Main
${label}
${cctimestamp}
full pom is here:
http://microemulator.svn.sourceforge.net/viewvc/microemulator/trunk/microemulator/microemulator/
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MAVENUPLOAD-1404) uploading bluecove-1.2.2 to The Central Repository
uploading bluecove-1.2.2 to The Central Repository -- Key: MAVENUPLOAD-1404 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1404 Project: maven-upload-requests Issue Type: Task Reporter: Vlad Skarzhevskyy http://bluecove.googlecode.com/files/bluecove-1.2.2-bundle.jar BlueCove is a LGPL licensed JSR-82 implementation on Java Standard Edition (J2SE) that currently interfaces with the Microsoft Bluetooth stack -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
