[jira] (WAGON-398) http spdy wagon
nambi sankaran created WAGON-398: Summary: http spdy wagon Key: WAGON-398 URL: https://jira.codehaus.org/browse/WAGON-398 Project: Maven Wagon Issue Type: New Feature Components: New Wagons Affects Versions: backlog Reporter: nambi sankaran Maven downloads the dependencies one-by-one on http. SPDY offers bidirectional multiplexing over the same TCP connection. It improves the connection efficiency. Since many maven users are using repository manager such as Nexus, the server can have SPDY support easily. Still maven needs to have SPDY support on http-wagon or a new http-spdy-wagon. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (WAGON-398) http spdy wagon
[ https://jira.codehaus.org/browse/WAGON-398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=326808#comment-326808 ] nambi sankaran commented on WAGON-398: -- The repository manager needs to support SPDY as well for this to work. The JIRA for sonatype nexus to suppor SPDY https://issues.sonatype.org/browse/NEXUS-5761 > http spdy wagon > --- > > Key: WAGON-398 > URL: https://jira.codehaus.org/browse/WAGON-398 > Project: Maven Wagon > Issue Type: New Feature > Components: New Wagons >Affects Versions: backlog >Reporter: nambi sankaran > > Maven downloads the dependencies one-by-one on http. SPDY offers > bidirectional multiplexing over the same TCP connection. It improves the > connection efficiency. Since many maven users are using repository manager > such as Nexus, the server can have SPDY support easily. Still maven needs to > have SPDY support on http-wagon or a new http-spdy-wagon. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MNG-4131) MavenXpp3Writer.write( writer, model ) does not write the for sections under when the "groupId" is "org.apache.maven.plugins"
MavenXpp3Writer.write( writer, model ) does not write the for
sections under when the "groupId" is
"org.apache.maven.plugins"
---
Key: MNG-4131
URL: http://jira.codehaus.org/browse/MNG-4131
Project: Maven 2
Issue Type: Bug
Components: Embedding
Affects Versions: 3.0-alpha-1, 2.0.9
Reporter: nambi sankaran
I need to update the some sections of a super pom file for every release.
Instead of writing a script, I am using maven-model library to read the Model
of the pom.xml and update my stuff.
then I am simply writing the file back into disk
Following is the code.
BufferedReader in = new BufferedReader( new
FileReader(pomFilePath) );
MavenXpp3Reader reader = new MavenXpp3Reader();
Model model = reader.read(in);
in.close();
DistributionManagement dMgmt =
model.getDistributionManagement();
DeploymentRepository repository = dMgmt.getRepository();
repository.setUrl(repositoryUrl);
// write the pom file
BufferedWriter out = new BufferedWriter(new FileWriter(
pomFilePath ));
MavenXpp3Writer writer = new MavenXpp3Writer();
writer.write(out, model);
MavenXpp3Writer.write( writer, model ) does not write the for
sections under when the "groupId" is
"org.apache.maven.plugins"
Following is the code that does the work
private void writePlugin(Plugin plugin, String tagName, XmlSerializer
serializer)
throws java.io.IOException
{
if ( plugin != null )
{
serializer.startTag( NAMESPACE, tagName );
if ( plugin.getGroupId() != null && !plugin.getGroupId().equals(
"org.apache.maven.plugins" ) )
{
serializer.startTag( NAMESPACE, "groupId" ).text(
plugin.getGroupId() ).endTag( NAMESPACE, "groupId" );
}
As you see, the writePlugin method does not write the "groupId" , when the
groupId is null or "org.apache.maven.plugins"
Is this intended or a bug?
--
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: (MDEPLOY-100) deploy:deploy-file fails from windows powershell
deploy:deploy-file fails from windows powershell Key: MDEPLOY-100 URL: http://jira.codehaus.org/browse/MDEPLOY-100 Project: Maven 2.x Deploy Plugin Issue Type: Bug Components: deploy:deploy-file Environment: windows powershell Reporter: nambi sankaran mvn deploy:deploy-file fails with authentication error when tried from windows powershell. The same command works from fine from normal windows command shell -- 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: (MDEPLOY-100) deploy:deploy-file fails from windows powershell
[ http://jira.codehaus.org/browse/MDEPLOY-100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=172969#action_172969 ] nambi sankaran commented on MDEPLOY-100: This is the stack trace, when run from windows powershell. It throws the error "maven-http-plugin" not found. this plugin is in the repository. hen executed from bash, windows cmd shell or cygwin , mvn deploy:deploy-file works just fine. PS C:\> mvn -X deploy:deploy-file -Durl=dav:http://repository.corp.ebay .com/bluewolf/snapshots -DrepositoryId=bluewolf -Dfile=ZXTM-API-eBay-1.0.jar -DpomFile=ZXTM-API-eBay-1.0.pom + Error stacktraces are turned on. Maven version: 2.0.9 Java version: 1.5.0 OS name: "windows server 2003" version: "5.2 build 3790 service pack 2" arch: "x86" Family: "dos" [DEBUG] Building Maven user-level plugin registry from: 'C:\Documents and Settings\djaisinghani\.m2\plugin-registry.xml' [DEBUG] Building Maven global-level plugin registry from: 'C:\ebox\maven-2.0.9\bin\..\conf\plugin-registry.xml' [INFO] Scanning for projects... [INFO] Searching repository for plugin with prefix: 'deploy'. [DEBUG] Loading plugin prefixes from group: com.ebay.ebox.plugins [DEBUG] Skipping disabled repository ebox.snapshots [DEBUG] Loading plugin prefixes from group: org.mortbay.jetty [DEBUG] Skipping disabled repository ebox.snapshots [DEBUG] Loading plugin prefixes from group: org.codehaus.mojo [DEBUG] Skipping disabled repository ebox.snapshots [DEBUG] Loading plugin prefixes from group: org.sonatype.maven.plugins [DEBUG] Skipping disabled repository ebox.snapshots [DEBUG] Loading plugin prefixes from group: org.apache.maven.plugins [DEBUG] Skipping disabled repository ebox.snapshots [DEBUG] Retrieving parent-POM: org.apache.maven.plugins:maven-plugins::7 for project: null:maven-deploy-plugin:maven-plu gin:2.3 from the repository. [DEBUG] Retrieving parent-POM: org.apache.maven:maven-plugin-surrogate-parent::5 for project: org.apache.maven.plugins:m aven-plugins:pom:7 from the repository. [DEBUG] Retrieving parent-POM: org.apache:apache::3 for project: org.apache.maven:maven-plugin-surrogate-parent:pom:5 fr om the repository. [INFO] Searching repository for plugin with prefix: 'http'. [DEBUG] Loading plugin prefixes from group: com.ebay.ebox.plugins [DEBUG] Loading plugin prefixes from group: org.mortbay.jetty [DEBUG] Loading plugin prefixes from group: org.codehaus.mojo [DEBUG] Loading plugin prefixes from group: org.sonatype.maven.plugins [DEBUG] Loading plugin prefixes from group: org.apache.maven.plugins [DEBUG] Skipping disabled repository ebox.snapshots [DEBUG] maven-http-plugin: using locally installed snapshot [DEBUG] Artifact not found - using stub model: Unable to determine the latest version org.apache.maven.plugins:maven-http-plugin:pom:LATEST [DEBUG] Using defaults for missing POM org.apache.maven.plugins:maven-http-plugin:pom:LATEST [DEBUG] maven-http-plugin: using locally installed snapshot [DEBUG] Artifact not found - using stub model: Unable to determine the release version org.apache.maven.plugins:maven-http-plugin:pom:RELEASE [DEBUG] Using defaults for missing POM org.apache.maven.plugins:maven-http-plugin:pom:RELEASE [INFO] [ERROR] BUILD ERROR [INFO] [INFO] The plugin 'org.apache.maven.plugins:maven-http-plugin' does not exist or no valid version could be found [INFO] [DEBUG] Trace org.apache.maven.lifecycle.LifecycleExecutionException: The plugin 'org.apache.maven.plugins:maven-http-plugin' does not exist or no valid version could be found at org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(DefaultLifecycleExecutor.java:1303) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.getMojoDescriptor(DefaultLifecycleExecutor.java:1542) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.segmentTaskListByAggregationNeeds(DefaultLifecycleExecuto r.java:405) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:137) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129) at org.apache.maven.cli.MavenCli.main(MavenCli.java:287) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:64) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:615) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.code
[jira] Created: (ARCHETYPE-157) Ability to generate empty directories
Ability to generate empty directories - Key: ARCHETYPE-157 URL: http://jira.codehaus.org/browse/ARCHETYPE-157 Project: Maven Archetype Issue Type: Improvement Components: Archetypes Environment: All Operating systems Reporter: nambi sankaran In my archetype, I would like to generate an empty directory that macthes with the package the user supplied The current version does not create the directory, if it is empty. As a workaround, I have added an empty file named ".file" to generate a directory with the package name. -- 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: (ARCHETYPE-158) Create a directory with name artiactId
Create a directory with name artiactId -- Key: ARCHETYPE-158 URL: http://jira.codehaus.org/browse/ARCHETYPE-158 Project: Maven Archetype Issue Type: Improvement Components: Archetypes Environment: All operating systems Reporter: nambi sankaran I need to generate a list of directories with name "artifactId" under /src/main/resources/. "artifactId" is the name of the project the user supplies, during archetypeng:create After generation the directory structure should look like this, /src/main/resources/ --> contract-> artifactId -> file.4cc --> sources -> en -> artifactId -> file.4cb --> sources -> fr -> artifactId -> file.4cb --> sources -> de -> artifactId -> file.4cb This feature would extremely valuable. thanks -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-4225) Plugin dependencies are incorrectly included as needed artifacts in IBM JDK 1.5 sr8 and IBM JDK 1.6
[ http://jira.codehaus.org/browse/MNG-4225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=182052#action_182052 ] nambi sankaran commented on MNG-4225: - This issue manifests when we use IBM JDK 1.6. But there are no problems with SUN JDK 1.6. Why do we see different behaviour between Different JDK vendors? > Plugin dependencies are incorrectly included as needed artifacts in IBM JDK > 1.5 sr8 and IBM JDK 1.6 > > > Key: MNG-4225 > URL: http://jira.codehaus.org/browse/MNG-4225 > Project: Maven 2 > Issue Type: Bug > Components: Dependencies >Affects Versions: 2.0.9 > Environment: OS : Windows Server 2003 > JDK: IBM JDK 1.5 sr8 edition and IBM JDK 1.6 >Reporter: Baback Nemazie >Priority: Blocker > Attachments: JavaMavenTest.zip > > > We have been using a "parent pom" that specifies the plugin dependencies for > our projects. This parent pom has been in use for more than a year. We have > been using IBM JDK 1.5 sr4 until recently, and we had no problems building > the parent pom. However for the upcoming release we upgraded to IBM JDK 1.5 > sr8. Upon upgrade to the sr8 edition, when we tried to build the parent pom, > the build process incorrectly tried to search for specified plugin > dependencies, and since these specified plugin dependencies are built AFTER > the parent pom is built the build process fails with the error message that > it could not find the plugin-dependencies in order to proceed with building > the parent pom. > We encountered the same issue with IBM JDK 1.6 as well. Since many of the > developers who use our product will be using IBM JDK 1.6, we need to resolve > this issue for both IBM JDK1.5 sr8 and IBM JDK 1.6. > We did NOT encounter this issue with the Sun JDK 1.6. This led us to approach > IBM to investigate the issue as it appeared that this maybe an IBM JDK > specific issue. We sent our test case to them, and they reported to us that > suspect that maven code could be depending on the hashmap ordering, which is > breaking the dependency check. > They instructed us to post this issue to the maven issue tracking and they > will follow up with the maven folks. > Attached is the test case to reproduce the problem. Please read the file > how_to_reproduce.txt in the attached. IBM folks will provide you with the > needed JDK's. -- 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
