[jira] (MNG-5764) Tolerate "soft" 404, check downloaded pom files
Laszlo Hornyak Kocka created MNG-5764: - Summary: Tolerate "soft" 404, check downloaded pom files Key: MNG-5764 URL: https://jira.codehaus.org/browse/MNG-5764 Project: Maven Issue Type: Bug Components: Dependencies Reporter: Laszlo Hornyak Kocka With maven 3.2 if the user downloads a pom/jar from external repository and the network proxy sends a "soft 404", the html-content of the response will be stored in the pom file. It needs some work to find out what went wrong. When downloading pom files, the content of the pom file could be parsed and the file should not be stored in the local maven cache. In such cases the artifact should not be downloaded either. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MNG-5764) Tolerate "soft" 404, check downloaded pom files
[ https://jira.codehaus.org/browse/MNG-5764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=363022#comment-363022 ] Laszlo Hornyak Kocka commented on MNG-5764: --- Hi Michael, 1. is usually a theoretical option, I have found pom files of different network providers "soft 404" on my laptop. Airports, public wifi providers. It is very unlikely that they would stop doing this for my request. 2. Running nexus on my laptop just to validate the downloaded pom files is probably too expensive solution. > Tolerate "soft" 404, check downloaded pom files > --- > > Key: MNG-5764 > URL: https://jira.codehaus.org/browse/MNG-5764 > Project: Maven > Issue Type: Bug > Components: Dependencies >Reporter: Laszlo Hornyak Kocka > > With maven 3.2 if the user downloads a pom/jar from external repository and > the network proxy sends a "soft 404", the html-content of the response will > be stored in the pom file. It needs some work to find out what went wrong. > When downloading pom files, the content of the pom file could be parsed and > the file should not be stored in the local maven cache. In such cases the > artifact should not be downloaded either. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] Updated: (MNG-2311) site plugin i18n HU
[ http://jira.codehaus.org/browse/MNG-2311?page=all ] Laszlo Hornyak Kocka updated MNG-2311: -- Attachment: project-info-report_hu.properties > site plugin i18n HU > --- > > Key: MNG-2311 > URL: http://jira.codehaus.org/browse/MNG-2311 > Project: Maven 2 > Type: Improvement > Components: Sites & Reporting > Reporter: Laszlo Hornyak Kocka > Attachments: project-info-report_hu.properties, > project-info-report_hu.properties, site-plugin_hu.properties > > > hungarian translation of the resource files as described in > http://maven.apache.org/plugins/maven-site-plugin/i18n.html -- 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: (CONTINUUM-722) Project should be built again if svn command fails
Project should be built again if svn command fails -- Key: CONTINUUM-722 URL: http://jira.codehaus.org/browse/CONTINUUM-722 Project: Continuum Type: Wish Components: Core system Versions: 1.0.3 Reporter: Laszlo Hornyak Kocka If the subversion server goes down, continuum sends a build error message, which is good, but it wont try to build it again after the subversion server goes online again, so one needs to rebuild the failed projects manualy. -- 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: (SCM-295) NullPointerException in VSS SCM provider
NullPointerException in VSS SCM provider Key: SCM-295 URL: http://jira.codehaus.org/browse/SCM-295 Project: Maven SCM Issue Type: Bug Components: maven-scm-provider-vss Affects Versions: 1.0-beta-4 Environment: Operating system : Windows XP(Service Pack 2) Java version : 1.5.0_11(Sun Microsystems Inc.) continuum 1.0.3 with the scm packages upgraded to 1.0-beta4 Reporter: Laszlo Hornyak Kocka org.apache.maven.continuum.scm.ContinuumScmException: Error while update sources. at org.apache.maven.continuum.scm.DefaultContinuumScm.updateProject(DefaultContinuumScm.java:272) at org.apache.maven.continuum.core.action.UpdateWorkingDirectoryFromScmContinuumAction.execute(UpdateWorkingDirectoryFromScmContinuumAction.java:58) at org.apache.maven.continuum.buildcontroller.DefaultBuildController.build(DefaultBuildController.java:166) at org.apache.maven.continuum.buildcontroller.BuildProjectTaskExecutor.executeTask(BuildProjectTaskExecutor.java:47) at org.codehaus.plexus.taskqueue.execution.ThreadedTaskQueueExecutor$ExecutorRunnable.run(ThreadedTaskQueueExecutor.java:103) at java.lang.Thread.run(Thread.java:595) Caused by: org.apache.maven.scm.ScmException: Exception while executing SCM command. at org.apache.maven.scm.command.AbstractCommand.execute(AbstractCommand.java:62) at org.apache.maven.scm.provider.vss.VssScmProvider.update(VssScmProvider.java:209) at org.apache.maven.scm.provider.AbstractScmProvider.update(AbstractScmProvider.java:418) at org.apache.maven.scm.provider.AbstractScmProvider.update(AbstractScmProvider.java:395) at org.apache.maven.continuum.scm.DefaultContinuumScm.updateProject(DefaultContinuumScm.java:242) ... 5 more Caused by: java.lang.NullPointerException at java.util.Calendar.setTime(Calendar.java:1032) at java.text.SimpleDateFormat.format(SimpleDateFormat.java:785) at java.text.SimpleDateFormat.format(SimpleDateFormat.java:778) at java.text.DateFormat.format(DateFormat.java:314) at org.apache.maven.scm.provider.vss.commands.changelog.VssHistoryCommand.buildCmdLine(VssHistoryCommand.java:114) at org.apache.maven.scm.provider.vss.commands.changelog.VssHistoryCommand.executeChangeLogCommand(VssHistoryCommand.java:52) at -- 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: (SCM-295) NullPointerException in VSS SCM provider
[ http://jira.codehaus.org/browse/SCM-295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_92245 ] Laszlo Hornyak Kocka commented on SCM-295: -- oops, seems to be duplicate with SCM-278 > NullPointerException in VSS SCM provider > > > Key: SCM-295 > URL: http://jira.codehaus.org/browse/SCM-295 > Project: Maven SCM > Issue Type: Bug > Components: maven-scm-provider-vss >Affects Versions: 1.0-beta-4 > Environment: Operating system : Windows XP(Service Pack 2) > Java version : 1.5.0_11(Sun Microsystems Inc.) > continuum 1.0.3 with the scm packages upgraded to 1.0-beta4 >Reporter: Laszlo Hornyak Kocka > > org.apache.maven.continuum.scm.ContinuumScmException: Error while update > sources. > at > org.apache.maven.continuum.scm.DefaultContinuumScm.updateProject(DefaultContinuumScm.java:272) > at > org.apache.maven.continuum.core.action.UpdateWorkingDirectoryFromScmContinuumAction.execute(UpdateWorkingDirectoryFromScmContinuumAction.java:58) > at > org.apache.maven.continuum.buildcontroller.DefaultBuildController.build(DefaultBuildController.java:166) > at > org.apache.maven.continuum.buildcontroller.BuildProjectTaskExecutor.executeTask(BuildProjectTaskExecutor.java:47) > at > org.codehaus.plexus.taskqueue.execution.ThreadedTaskQueueExecutor$ExecutorRunnable.run(ThreadedTaskQueueExecutor.java:103) > at java.lang.Thread.run(Thread.java:595) > Caused by: org.apache.maven.scm.ScmException: Exception while executing SCM > command. > at > org.apache.maven.scm.command.AbstractCommand.execute(AbstractCommand.java:62) > at > org.apache.maven.scm.provider.vss.VssScmProvider.update(VssScmProvider.java:209) > at > org.apache.maven.scm.provider.AbstractScmProvider.update(AbstractScmProvider.java:418) > at > org.apache.maven.scm.provider.AbstractScmProvider.update(AbstractScmProvider.java:395) > at > org.apache.maven.continuum.scm.DefaultContinuumScm.updateProject(DefaultContinuumScm.java:242) > ... 5 more > Caused by: java.lang.NullPointerException > at java.util.Calendar.setTime(Calendar.java:1032) > at java.text.SimpleDateFormat.format(SimpleDateFormat.java:785) > at java.text.SimpleDateFormat.format(SimpleDateFormat.java:778) > at java.text.DateFormat.format(DateFormat.java:314) > at > org.apache.maven.scm.provider.vss.commands.changelog.VssHistoryCommand.buildCmdLine(VssHistoryCommand.java:114) > at > org.apache.maven.scm.provider.vss.commands.changelog.VssHistoryCommand.executeChangeLogCommand(VssHistoryCommand.java:52) > at -- 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-402) Enable linkedResources in .project file
Enable linkedResources in .project file
---
Key: MECLIPSE-402
URL: http://jira.codehaus.org/browse/MECLIPSE-402
Project: Maven 2.x Eclipse Plugin
Issue Type: New Feature
Components: Core : Multi-projects
Reporter: Laszlo Hornyak Kocka
It would be very helpful if eclipse plugin could generate linkedResources tag
for the generated project file, pointing e.g. to an another project of a
multimodule maven project
src/main/webapp/flashclient.swf
1
/home/kocka/blabla/bla/trunk/flashclient/target/flashclient-1.0-SNAPSHOT.swf
generated from this configuration
org.apache.maven.plugins
maven-eclipse-plugin
1.5
../flashclient/target/flashclient-${version}.swf
--
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: (SCM-206) add starteam-settings.xml support
[ http://jira.codehaus.org/browse/SCM-206?page=comments#action_78635 ] Laszlo Hornyak Kocka commented on SCM-206: -- where can one find documentation about the xml format of starteam-settings.xml? > add starteam-settings.xml support > - > > Key: SCM-206 > URL: http://jira.codehaus.org/browse/SCM-206 > Project: Maven SCM > Issue Type: New Feature > Components: maven-scm-provider-starteam >Affects Versions: 1.0-beta-3 > Environment: XP starteam >Reporter: Dan Tran > Assigned To: Dan Tran > Fix For: 1.0 > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MNG-2748) jackrabit pom fix suggestions
jackrabit pom fix suggestions - Key: MNG-2748 URL: http://jira.codehaus.org/browse/MNG-2748 Project: Maven 2 Issue Type: Bug Components: Artifacts Reporter: Laszlo Hornyak Kocka Attachments: jackrabbit-poms.tar.gz mandatory 'groupId' and 'version' tags missing, some dependency has strange version (and it looks trivial which version it should use) attached poms fix the issues -- 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: (MEV-485) jackrabit pom fix suggestions
[ http://jira.codehaus.org/browse/MEV-485?page=comments#action_84636 ]
Laszlo Hornyak Kocka commented on MEV-485:
--
In
http://repo1.maven.org/maven2/org/apache/jackrabbit/jackrabbit-jcr-client/1.1.1/jackrabbit-jcr-client-1.1.1.pom
and
http://repo1.maven.org/maven2/org/apache/jackrabbit/jackrabbit-jcr-webdav/1.1.1/jackrabbit-jcr-webdav-1.1.1.pom
groupid and version is missing.
Also in
http://repo1.maven.org/maven2/org/apache/jackrabbit/jackrabbit-core/1.1.1/jackrabbit-core-1.1.1.pom
"
org.apache.jackrabbit
jackrabbit-jcr-commons
${jackrabbit.build.version.jackrabbit}
" I think jackrabbit-jcr-commons-1.1.1.jar is tested against
jackrabbit version 1.1.1 components.
I will attach a test pom soon.
> jackrabit pom fix suggestions
> -
>
> Key: MEV-485
> URL: http://jira.codehaus.org/browse/MEV-485
> Project: Maven Evangelism
> Issue Type: Bug
> Components: Invalid POM
>Reporter: Laszlo Hornyak Kocka
> Attachments: jackrabbit-poms.tar.gz
>
>
> mandatory 'groupId' and 'version' tags missing, some dependency has strange
> version (and it looks trivial which version it should use)
> attached poms fix the issues
--
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: (MEV-485) jackrabit pom fix suggestions
[ http://jira.codehaus.org/browse/MEV-485?page=comments#action_84637 ] Laszlo Hornyak Kocka commented on MEV-485: -- http://maven.apache.org/POM/4.0.0"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd";> 4.0.0 com.bla bla jar 1.0-SNAPSHOT bla-bla http://blabla.com junit junit 3.8.1 test commons-dbcp commons-dbcp 1.2.1 org.apache.jackrabbit jackrabbit-jcr-client 1.1.1 In my previous comment: the dependency problem is not in the core pom, but in http://repo1.maven.org/maven2/org/apache/jackrabbit/jackrabbit-jcr-webdav/1.1.1/jackrabbit-jcr-webdav-1.1.1.pom A diff may explain better... > jackrabit pom fix suggestions > - > > Key: MEV-485 > URL: http://jira.codehaus.org/browse/MEV-485 > Project: Maven Evangelism > Issue Type: Bug > Components: Invalid POM >Reporter: Laszlo Hornyak Kocka > Attachments: jackrabbit-poms.tar.gz > > > mandatory 'groupId' and 'version' tags missing, some dependency has strange > version (and it looks trivial which version it should use) > attached poms fix the issues -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MNG-2311) site plugin i18n HU
site plugin i18n HU --- Key: MNG-2311 URL: http://jira.codehaus.org/browse/MNG-2311 Project: Maven 2 Type: Improvement Components: Sites & Reporting Reporter: Laszlo Hornyak Kocka Attachments: project-info-report_hu.properties, site-plugin_hu.properties hungarian translation of the resource files as described in http://maven.apache.org/plugins/maven-site-plugin/i18n.html -- 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-2170) Packaged Maven Documentation for Download
[ http://jira.codehaus.org/browse/MNG-2170?page=comments#action_65681 ] Laszlo Hornyak Kocka commented on MNG-2170: --- What about the book? http://library.mergere.com/m2book_download.jsp requires free registration and they send promotion mails, but the book is cool > Packaged Maven Documentation for Download > - > > Key: MNG-2170 > URL: http://jira.codehaus.org/browse/MNG-2170 > Project: Maven 2 > Type: Wish > Components: Documentation: General > Environment: all environments > Reporter: Hans Baier > > > Hello, > I am sorely missing packaged maven documentation for download > on the maven project site. > Every time I want to look something up, > I have to go online. > Thank you for the great software! -- 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-2278) Maven 2 site plugin ignoring powered-by tag
[ http://jira.codehaus.org/browse/MNG-2278?page=comments#action_65710 ] Laszlo Hornyak Kocka commented on MNG-2278: --- Is it planed to update the site plugin with the new version that supports the powered--by tag? > Maven 2 site plugin ignoring powered-by tag > --- > > Key: MNG-2278 > URL: http://jira.codehaus.org/browse/MNG-2278 > Project: Maven 2 > Type: Improvement > Components: Sites & Reporting > Versions: 2.0.4 > Reporter: Roberto Lo Giacco > Assignee: Brett Porter > Priority: Minor > Attachments: maven-site.patch > > > The site-plugin completely ignores the optional powered-by tag(s) as defined > in the old navigation.xml site descriptor. -- 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: (CONTINUUM-663) Google Summer Of Code 2006 proposal for Continuum Eclipse Plugin
[ http://jira.codehaus.org/browse/CONTINUUM-663?page=comments#action_65998 ] Laszlo Hornyak Kocka commented on CONTINUUM-663: Hi! I wrote a plugin continuum-plugin for eclipse, use it as inspiration if you like. It was under http://www.codehaus.org/~kocka/cm-plugin/ screenshots of version 0.0.1: http://www.jhacks.hu/space/cm-plugin/cm-preferences.gif and http://www.jhacks.hu/space/cm-plugin/cm-view.gif > Google Summer Of Code 2006 proposal for Continuum Eclipse Plugin > - > > Key: CONTINUUM-663 > URL: http://jira.codehaus.org/browse/CONTINUUM-663 > Project: Continuum > Type: New Feature > Environment: Maven 2.0.x, Continuum 1.0.x, Eclipse 3.2 > Reporter: Rahul Thakur > Attachments: Continuum-Eclipse-plugin-Google-SOC2006-proposal.txt, > Continuum-Eclipse-plugin-Google-SOC2006-proposal.txt > > Original Estimate: 8 weeks > Remaining: 8 weeks > > It is proposed for Google SOC 2006 to develop a Continuum Eclipse Plugin that > could be used by Eclipse users to manage project builds on a remote Continuum > server. -- 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: (CONTINUUM-713) re-enabling xfire?
re-enabling xfire? -- Key: CONTINUUM-713 URL: http://jira.codehaus.org/browse/CONTINUUM-713 Project: Continuum Type: Wish Versions: 1.0.2, 1.0.3 Reporter: Laszlo Hornyak Kocka As far as I remember XFire-based ws interface was disabled by default from continuum in release 1.0.2, and I did not manange to re-enable it. XFire 1.1 has motm support, so the build data can be streamed to clients e.g. for IDE-plugins... -- 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: (CONTINUUM-663) Google Summer Of Code 2006 proposal for Continuum Eclipse Plugin
[ http://jira.codehaus.org/browse/CONTINUUM-663?page=comments#action_66019 ] Laszlo Hornyak Kocka commented on CONTINUUM-663: Hi! It was deleted at the codehaus server crash, I attach it to this issue. It works with continuum 1.0.2 and eclipse 3.1 Also, the netbeans-maven2 plugin has a very good functionality which may be good for a begining. > Google Summer Of Code 2006 proposal for Continuum Eclipse Plugin > - > > Key: CONTINUUM-663 > URL: http://jira.codehaus.org/browse/CONTINUUM-663 > Project: Continuum > Type: New Feature > Environment: Maven 2.0.x, Continuum 1.0.x, Eclipse 3.2 > Reporter: Rahul Thakur > Attachments: Continuum-Eclipse-plugin-Google-SOC2006-proposal.txt, > Continuum-Eclipse-plugin-Google-SOC2006-proposal.txt > > Original Estimate: 8 weeks > Remaining: 8 weeks > > It is proposed for Google SOC 2006 to develop a Continuum Eclipse Plugin that > could be used by Eclipse users to manage project builds on a remote Continuum > server. -- 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: (CONTINUUM-663) Google Summer Of Code 2006 proposal for Continuum Eclipse Plugin
[ http://jira.codehaus.org/browse/CONTINUUM-663?page=all ] Laszlo Hornyak Kocka updated CONTINUUM-663: --- Attachment: cm-plugin.tar.gz > Google Summer Of Code 2006 proposal for Continuum Eclipse Plugin > - > > Key: CONTINUUM-663 > URL: http://jira.codehaus.org/browse/CONTINUUM-663 > Project: Continuum > Type: New Feature > Environment: Maven 2.0.x, Continuum 1.0.x, Eclipse 3.2 > Reporter: Rahul Thakur > Attachments: Continuum-Eclipse-plugin-Google-SOC2006-proposal.txt, > Continuum-Eclipse-plugin-Google-SOC2006-proposal.txt, cm-plugin.tar.gz > > Original Estimate: 8 weeks > Remaining: 8 weeks > > It is proposed for Google SOC 2006 to develop a Continuum Eclipse Plugin that > could be used by Eclipse users to manage project builds on a remote Continuum > server. -- 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: (CONTINUUM-663) Google Summer Of Code 2006 proposal for Continuum Eclipse Plugin
[ http://jira.codehaus.org/browse/CONTINUUM-663?page=comments#action_66024 ] Laszlo Hornyak Kocka commented on CONTINUUM-663: A quick comparison with the requirements 3-1) Allow setup of connection profiles to multiple Continuum instances. Not supported. 3-2) Display list of currently added Maven projects. Supported. 3-3) Allow user to ADD/EDIT/DELETE a Maven project. not supported. 3-4) Allow user to trigger/force a manual build for a Project. Supported. 3-5) Allow user to ADD/VIEW/EDIT build definitions for a selected Maven project. not supported 3-6) Provide a user-friendly interface to enable user to set up a Cron-based schedule for a build. not supported 3-7) Obtain build results for a given project build. supported in a tricky way, with a browser, as far as I know it should not work with XML-RPC since build logs can grow really large, which would lead to OOMs both client and server side, see also CONTINUUM-713 It uses my own xml-rpc wrapper for continuum, the one maintained by the mevenide project would be better imho. > Google Summer Of Code 2006 proposal for Continuum Eclipse Plugin > - > > Key: CONTINUUM-663 > URL: http://jira.codehaus.org/browse/CONTINUUM-663 > Project: Continuum > Type: New Feature > Environment: Maven 2.0.x, Continuum 1.0.x, Eclipse 3.2 > Reporter: Rahul Thakur > Attachments: Continuum-Eclipse-plugin-Google-SOC2006-proposal.txt, > Continuum-Eclipse-plugin-Google-SOC2006-proposal.txt, cm-plugin.tar.gz > > Original Estimate: 8 weeks > Remaining: 8 weeks > > It is proposed for Google SOC 2006 to develop a Continuum Eclipse Plugin that > could be used by Eclipse users to manage project builds on a remote Continuum > server. -- 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: (CONTINUUM-663) Google Summer Of Code 2006 proposal for Continuum Eclipse Plugin
[ http://jira.codehaus.org/browse/CONTINUUM-663?page=comments#action_66035 ] Laszlo Hornyak Kocka commented on CONTINUUM-663: yes, ASL is ok. confluence... > Google Summer Of Code 2006 proposal for Continuum Eclipse Plugin > - > > Key: CONTINUUM-663 > URL: http://jira.codehaus.org/browse/CONTINUUM-663 > Project: Continuum > Type: New Feature > Environment: Maven 2.0.x, Continuum 1.0.x, Eclipse 3.2 > Reporter: Rahul Thakur > Attachments: Continuum-Eclipse-plugin-Google-SOC2006-proposal.txt, > Continuum-Eclipse-plugin-Google-SOC2006-proposal.txt, cm-plugin.tar.gz > > Original Estimate: 8 weeks > Remaining: 8 weeks > > It is proposed for Google SOC 2006 to develop a Continuum Eclipse Plugin that > could be used by Eclipse users to manage project builds on a remote Continuum > server. -- 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
