[jira] Commented: (WAGON-82) wagon-webdav does not set http-proxy correctly
[ http://jira.codehaus.org/browse/WAGON-82?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_106820 ] Brett Porter commented on WAGON-82: --- ok, I successfully applied this - but I'm not entirely comfortable with it. Firstly, I can't get that change into Maven trunk/branch until wagon would be released with it's changes. However, the upshot of the patch is that the webdav wagon ignores the proxy that is passed in. I think it would be better to take the earlier solution provided by Jochen where: a) we fix the wagon manager to pass the correct proxy in (presumably it's giving dav instead of http - surely we can figure that out), or otherwise b) pass in all the proxies and let the wagon decide which to use. I'll have to take a closer look at this next week - sorry. > wagon-webdav does not set http-proxy correctly > -- > > Key: WAGON-82 > URL: http://jira.codehaus.org/browse/WAGON-82 > Project: wagon > Issue Type: Bug > Components: wagon-webdav >Affects Versions: 1.0-beta-2 > Environment: any system >Reporter: Marc Wilhelm >Assignee: Brett Porter >Priority: Blocker > Attachments: WAGON-82-maven-artifact-manager.patch, > WAGON-82-tested-maven-artifact-manager.patch, WAGON-82-tested-wagon.patch, > WAGON-82-wagon.patch, wagon-webdav.patch > > > Webdav connections through a http-proxy are currently not possible. > The webdav provider opens first a connection to the target system and checks > after this, if a proxy should be used. > To fix this in the method > "org.apache.maven.wagon.providers.webdav.WebdavWagon#openConnection()" the > call "webdavResource = new CorrectedWebdavResource( httpURL );" must be > changed into "webdavResource = new CorrectedWebdavResource( );" and after > configuring the http-proxy the method call > "webdavResource.setHttpURL(httpURL);" must be added. -- 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-3150) Command line -f option should propagate to module poms.
[ http://jira.codehaus.org/browse/MNG-3150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_106823 ] Arik Kfir commented on MNG-3150: Why not use profiles for this? > Command line -f option should propagate to module poms. > --- > > Key: MNG-3150 > URL: http://jira.codehaus.org/browse/MNG-3150 > Project: Maven 2 > Issue Type: Improvement > Components: Command Line >Reporter: Paul Gier > Attachments: MNG-3150-maven-core-r573613.patch > > > I have a multi module project where I would like to have parrallel builds. > The default pom.xml build would be using jdk1.5 or jdk6, and the parrallel > build pom would be for creating retro compiled jdk14 artifacts. So the pom > for this build would be "pom-jdk14.xml". I've explored other options such as > using a classifier for the retro translated artifact, and using profiles to > choose between jdk1.5 and jdk1.4 builds. But both of these have problems > that I can't get around without a lot of difficulty. > Using two separate poms works great for me for a single module project, but > for a multi module project, I have no way to tell the modules to pick up a > different pom.xml file. > So for my multi module build I would like to be able to say > mvn -f pom-jdk14.xml install > And each module should then look for it's own pom-jdk14.xml. This could be > made into the default behaviour of the "-f" option, or a new option could be > introduced like "-fg" to use the other pom file globally across all the > module. -- 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-3190) Need to fix hyperlinks at top of Getting Started Guide
[ http://jira.codehaus.org/browse/MNG-3190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_106826 ] Dennis Lundberg commented on MNG-3190: -- Did you even read the comment that was made when the issue was closed? This issue is a duplicate. There is no need to keep identical issues open. > Need to fix hyperlinks at top of Getting Started Guide > -- > > Key: MNG-3190 > URL: http://jira.codehaus.org/browse/MNG-3190 > Project: Maven 2 > Issue Type: Bug > Components: Documentation: Guides >Affects Versions: Documentation Deficit >Reporter: Glen Mazza >Priority: Minor > > Hello, the hyperlinks under the "Sections" heading at the top of > http://maven.apache.org/guides/getting-started/index.html do not > work--something is wrong with their anchor values. If these hyperlinks could > be fixed, it would be a *great* help. -- 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-3074) Anchor links in several documentations do not work
[ http://jira.codehaus.org/browse/MNG-3074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_106825 ] Dennis Lundberg commented on MNG-3074: -- Anchor links are due to a bug in Doxia. This will be solved by doxia 1.0-alpha-9. > Anchor links in several documentations do not work > -- > > Key: MNG-3074 > URL: http://jira.codehaus.org/browse/MNG-3074 > Project: Maven 2 > Issue Type: Bug > Components: Documentation: General >Reporter: Rick Janda >Priority: Minor > > In the online documentation User Centre, the anchor links from the table of > contents at the beginning of the Settings Reference and the POM Reference do > not work at all. Also the anchor links to the different sections at the > beginning of the Getting Started Guide do not work. -- 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: (MSOURCES-21) Allow classes to be bundled with the source code
[ http://jira.codehaus.org/browse/MSOURCES-21?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_106827 ] Benjamin Bentmann commented on MSOURCES-21: --- There seems to be a problem with your patch: The mojos might not see any class files for packaging since the mojos only depend on the "generate-source" phase but class files are not created until "compile" phase. However, increasing the lifecycle requirements of the mojos will slow down the plugin and might make it unattractive to many users with simpler use cases. For the above reasons, I would not expect your patch to get included. Instead, I suggest you have a look at the [maven-assembly-plugin|http://maven.apache.org/plugins/maven-assembly-plugin/]. Its configuration is a bit more expensive but it can handle quite a lot of packaging stuff. Because it requires the "package" phase, there should be no problems about inclusion of compiled classes. > Allow classes to be bundled with the source code > > > Key: MSOURCES-21 > URL: http://jira.codehaus.org/browse/MSOURCES-21 > Project: Maven 2.x Source Plugin > Issue Type: New Feature >Affects Versions: 2.0.3 >Reporter: Tom Schneider >Priority: Minor > Attachments: sourceplugin-includeClasses.patch > > > We have the need to bundle the compiled class files with the source code and > other resources. So I created a patch that adds a new configuration point > (includeClasses) that when set to true, will bundle not only the source code > and resources, but also the generated 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] Commented: (MPA-105) Create a new JIRA project for doxia-sitetools
[ http://jira.codehaus.org/browse/MPA-105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_106828 ] Vincent Siveton commented on MPA-105: - Lukas proposed a better name: DOXIASITETOOLS http://jira.codehaus.org/browse/DOXIASITETOOLS > Create a new JIRA project for doxia-sitetools > - > > Key: MPA-105 > URL: http://jira.codehaus.org/browse/MPA-105 > Project: Maven Project Administration > Issue Type: Bug > Components: Issue Management >Reporter: Vincent Siveton >Assignee: Brett Porter > Fix For: 2007-q3 > > > We need another project for doxia-sitetools. > http://www.nabble.com/Releasing-Doxia-tf4307508.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: (MSOURCES-23) test-jar misses sources from "generate-test-sources" phase
test-jar misses sources from "generate-test-sources" phase -- Key: MSOURCES-23 URL: http://jira.codehaus.org/browse/MSOURCES-23 Project: Maven 2.x Source Plugin Issue Type: Improvement Affects Versions: 2.0.3 Environment: Maven 2.0.7 Reporter: Benjamin Bentmann Priority: Minor When the goal source:test-jar is run directly from the command-line, the plugin will miss source files that get generated during the "generate-test-sources" phase as the mojo currently only requires the "generate-sources" phase. Though simply increasing the mojos lifecycle requirement would solve the problem, it kind of looks ugly to have the lengthy and potentially failing "compile" phase get run just to package test sources (first time I realize practical limitations of Maven's simple waterfall lifecycle compared to partially ordered goals...). An additional mojo like "generated-test-jar" might therefore be the best solution to keep the majority of use-cases fast but support the more sophisticated cases as well. -- 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: (MSOURCES-24) jar misses resources from "generate-resources" phase
jar misses resources from "generate-resources" phase Key: MSOURCES-24 URL: http://jira.codehaus.org/browse/MSOURCES-24 Project: Maven 2.x Source Plugin Issue Type: Improvement Affects Versions: 2.0.3 Environment: Maven 2.0.7 Reporter: Benjamin Bentmann Priority: Minor When the goal source:jar is run directly from the command-line, the plugin will miss resource files that get generated during the "generate-resources" phase as the mojo currently only requires the "generate-sources" phase. Increasing the lifecycle requirements of the mojo to "generate-resources" would also cause "process-sources" to get run. I cannot judge whether this would cause any harm to existing plugin users. One might further consider to increase the lifecycle requirement to "process-resources" so that both sources and resources are in a consistent state before being packaged. Taking [MSOURCES-22|http://jira.codehaus.org/browse/MSOURCES-22] into account, it might be advisable to separate the packaging of sources and resources into two distinct mojos. The first mojo would only package the (compile) source files and would therefore only require the "generate-/process-sources" phase. The second mojo would package the source files and the resources (similar to the current jar goal), requiring the phase "generate-/process-resources". In contrast to adding a configuration option to exclude resources, introducing a new mojo would allow to tune the lifecycle requirements, hopefully supporting more use-cases for the plugin. -- 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-3190) Need to fix hyperlinks at top of Getting Started Guide
[ http://jira.codehaus.org/browse/MNG-3190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_106829 ] Glen Mazza commented on MNG-3190: - Yes, I did see it--but the original report is from June! Does no one on the Maven team really have the five-ten minutes to fix this problem? This is a gratuitous pain to newbie developers just starting with Maven, and for corporations debating their usage of this product, having dead links that don't work on a vital introductory page reflect poorly on the product and how well it is supported--it's like getting a resume filled with typos. It detracts from whatever else you guys are working on further downstream. You do developers no favor when you require them to have to explain to their bosses, when trying to get them to approve Maven, "Oh, um, ignore the fact that the hyperlinks at the top are dead--this is still a really well-maintained and -supported product we can rely on." I would supply a patch but I don't know the Maven source code, it would take me 10 times longer to fix. Regardless, I already contribute quite a bit to incubating Apache CXF today--freeing up time for Dan Kulp to help out more on Maven ;-)--so it is not cost-effective to have me studying Maven code at a cost of contribution time to the CXF project. Anyway, I do hope the Maven team can get this problem fixed soon. Regards, Glen > Need to fix hyperlinks at top of Getting Started Guide > -- > > Key: MNG-3190 > URL: http://jira.codehaus.org/browse/MNG-3190 > Project: Maven 2 > Issue Type: Bug > Components: Documentation: Guides >Affects Versions: Documentation Deficit >Reporter: Glen Mazza >Priority: Minor > > Hello, the hyperlinks under the "Sections" heading at the top of > http://maven.apache.org/guides/getting-started/index.html do not > work--something is wrong with their anchor values. If these hyperlinks could > be fixed, it would be a *great* help. -- 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-3190) Need to fix hyperlinks at top of Getting Started Guide
[ http://jira.codehaus.org/browse/MNG-3190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_106831 ] Dennis Lundberg commented on MNG-3190: -- This issue can not be fixed by patching one of the documentation files. The problem lies in the site generation framework doxia. The bug has been fixed there and we are working to get a release out as soon as we can. > Need to fix hyperlinks at top of Getting Started Guide > -- > > Key: MNG-3190 > URL: http://jira.codehaus.org/browse/MNG-3190 > Project: Maven 2 > Issue Type: Bug > Components: Documentation: Guides >Affects Versions: Documentation Deficit >Reporter: Glen Mazza >Priority: Minor > > Hello, the hyperlinks under the "Sections" heading at the top of > http://maven.apache.org/guides/getting-started/index.html do not > work--something is wrong with their anchor values. If these hyperlinks could > be fixed, it would be a *great* help. -- 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-3190) Need to fix hyperlinks at top of Getting Started Guide
[ http://jira.codehaus.org/browse/MNG-3190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_106833 ] Glen Mazza commented on MNG-3190: - I see. Thanks for the explanation. Glen > Need to fix hyperlinks at top of Getting Started Guide > -- > > Key: MNG-3190 > URL: http://jira.codehaus.org/browse/MNG-3190 > Project: Maven 2 > Issue Type: Bug > Components: Documentation: Guides >Affects Versions: Documentation Deficit >Reporter: Glen Mazza >Priority: Minor > > Hello, the hyperlinks under the "Sections" heading at the top of > http://maven.apache.org/guides/getting-started/index.html do not > work--something is wrong with their anchor values. If these hyperlinks could > be fixed, it would be a *great* help. -- 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] Closed: (MNG-3088) update the assembly name
[ http://jira.codehaus.org/browse/MNG-3088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl closed MNG-3088. -- Resolution: Fixed Changed for both the branch and trunk. > update the assembly name > > > Key: MNG-3088 > URL: http://jira.codehaus.org/browse/MNG-3088 > Project: Maven 2 > Issue Type: Task > Components: Bootstrap & Build >Affects Versions: 2.0.7 >Reporter: Brett Porter >Assignee: Jason van Zyl > Fix For: 2.0.8 > > > We should update the assembly names to be apache-maven-* instead of just > maven-* > (see dev@ for discussion, > http://mail-archives.apache.org/mod_mbox/maven-dev/200706.mbox/[EMAIL > PROTECTED]) -- 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: (DOXIA-151) IOException when using skins that don't have a css directory
IOException when using skins that don't have a css directory Key: DOXIA-151 URL: http://jira.codehaus.org/browse/DOXIA-151 Project: Maven Doxia Issue Type: Bug Components: Site Renderer Affects Versions: 1.0-alpha-9 Reporter: Dennis Lundberg Assignee: Dennis Lundberg Fix For: 1.0-alpha-9 >From IRC: HandyAndE: well, the skin works on beta-6-SNAPSHOT, but it fails if I don't have a src/site/resource/css/site.css in _every_ module -- 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] Closed: (DOXIA-151) IOException when using skins that don't have a css directory
[ http://jira.codehaus.org/browse/DOXIA-151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg closed DOXIA-151. - Resolution: Fixed Fixed in r573873. > IOException when using skins that don't have a css directory > > > Key: DOXIA-151 > URL: http://jira.codehaus.org/browse/DOXIA-151 > Project: Maven Doxia > Issue Type: Bug > Components: Site Renderer >Affects Versions: 1.0-alpha-9 >Reporter: Dennis Lundberg >Assignee: Dennis Lundberg > Fix For: 1.0-alpha-9 > > > From IRC: > HandyAndE: well, the skin works on beta-6-SNAPSHOT, but it fails if I don't > have a src/site/resource/css/site.css in _every_ module -- 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: (MNG-2234) activeProfile in ~/.m2/settings.xml is ignored when profiles section is missing or empty
[ http://jira.codehaus.org/browse/MNG-2234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl updated MNG-2234: --- Fix Version/s: (was: 2.0.x) 2.1-alpha-1 After chatting with John, we can turn this on because a proposal is forth coming that will limit downstream profile activation to os, jdk, and activeByDefault. Everything else should be ignored. So we can let users turn on profiles in their settings but this begs the question, what is not being triggered by default in the project you're working on? > activeProfile in ~/.m2/settings.xml is ignored when profiles section is > missing or empty > > > Key: MNG-2234 > URL: http://jira.codehaus.org/browse/MNG-2234 > Project: Maven 2 > Issue Type: Bug > Components: Profiles, Settings >Affects Versions: 2.0.4 >Reporter: Manfred Geiler >Assignee: Jason van Zyl > Fix For: 2.1-alpha-1 > > > When i have this settings.xml file in my user home dir, the activeProfile > setting is simply ignored by Maven: > > > env-test > > > Adding an empty profiles section does not help: > > > > > env-test > > > Well, adding a dummy profile makes it work: > > > > dummy > > > > env-test > > > Funny, isn't it? > Regards, > Manfred -- 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-1708) Synchronization of JiBX repository with the central repository
Synchronization of JiBX repository with the central repository -- Key: MAVENUPLOAD-1708 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1708 Project: maven-upload-requests Issue Type: Task Reporter: Jerome Bernard The attached script follows the instructions for automatic synchronization. -- 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] Closed: (MNG-1985) Triggering Profiles bugs
[ http://jira.codehaus.org/browse/MNG-1985?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl closed MNG-1985. -- Resolution: Fixed This is the correct behavior. When you have a profile that is activeByDefault it means that it will be knocked out once another profile is activated. This profile is used when no other profiles are activated. And profile chaining is not supported. > Triggering Profiles bugs > > > Key: MNG-1985 > URL: http://jira.codehaus.org/browse/MNG-1985 > Project: Maven 2 > Issue Type: Bug > Components: Profiles >Affects Versions: 2.0.2 > Environment: windows2000 maven 2.02 >Reporter: pinghe >Priority: Critical > Fix For: 2.0.x > > > ===env 1, > inside pom.xml > > > env-common > > true > > > > os-win32 > > true > > > performRelease > > > > > env-prod > > > performRelease > > > > > exec: mvn projecthelp:active-profiles > output: > - env-common (source: pom) > - os-win32 (source: pom) > exec: mvn projecthelp:active-profiles -DperformRelease > output: > - env-prod (source: pom) > - os-win32 (source: pom) > expect: > - env-prod (source: pom) > - os-win32 (source: pom) > - env-common (source: pom) > ===env 2: > inside pom.xml > > > env-common > > true > > > > os-win32 > > true > > windows > > > performRelease > > > > > env-prod > > > performRelease > > > > > exec: mvn projecthelp:active-profiles > output: > - os-win32 (source: pom) > expect: > - env-prod (source: pom) > - os-win32 (source: pom) -- 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] Closed: (MNG-2294) If /project/parent/relativePath fails to resolve, no error is reported.
[ http://jira.codehaus.org/browse/MNG-2294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl closed MNG-2294. -- Resolution: Fixed This is by design as noted. The only way this could be addressed is to have a flag to validate that the entire project is checked out. That a project root is on disk. > If /project/parent/relativePath fails to resolve, no error is reported. > --- > > Key: MNG-2294 > URL: http://jira.codehaus.org/browse/MNG-2294 > Project: Maven 2 > Issue Type: Bug > Components: Logging >Affects Versions: 2.0.4 >Reporter: David Smiley >Assignee: Maria Odea Ching > Fix For: 2.0.x > > Original Estimate: 15 hours > Remaining Estimate: 15 hours > > If I have a bad /project/parent/relativePath specified, maven does not tell > me. Instead the build proceeds as if there is no parent. The build should > fail if the parent can't be resolved. -- 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] Closed: (CONTINUUM-1430) Split forms for environment variables and Ant/Maven/JDK installations
[ http://jira.codehaus.org/browse/CONTINUUM-1430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy closed CONTINUUM-1430. --- Resolution: Fixed apply in svn rev 573895 > Split forms for environment variables and Ant/Maven/JDK installations > - > > Key: CONTINUUM-1430 > URL: http://jira.codehaus.org/browse/CONTINUUM-1430 > Project: Continuum > Issue Type: Improvement > Components: Web - UI >Affects Versions: 1.1-beta-1, 1.1-beta-2 >Reporter: Wendy Smoak >Assignee: Olivier Lamy > Fix For: 1.1-beta-3 > > Attachments: CONTINUUM-1430 > > > As discussed on the dev list: > http://www.nabble.com/Splitting-up-the-Installations-form-t4375197.html > I think the form for adding a new Installation should be split up into one > form for environment variables, and another for the Ant/Maven/JDK > installations. > The current web UI is confusing, we have a field marked as required when it > usually isn't, necessitating a long field label to try to explain the > situation. -- 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] Closed: (MNG-1348) includes on resource tag not documented as being a list
[ http://jira.codehaus.org/browse/MNG-1348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg closed MNG-1348. Assignee: Dennis Lundberg Resolution: Fixed The documentation for resource now says: includesA list of patterns to include, e.g. **/*.xml. > includes on resource tag not documented as being a list > --- > > Key: MNG-1348 > URL: http://jira.codehaus.org/browse/MNG-1348 > Project: Maven 2 > Issue Type: Bug > Components: Documentation: General >Reporter: Ryan Sonnek >Assignee: Dennis Lundberg > Fix For: Documentation Deficit > > > according to the product documentation at > http://maven.apache.org/maven2/maven-model/maven.html each resource should be > able to specify includes. maven errors out unless the inclues is moved out > of "resource" and into the "resources" tag. > example model: > > > src/main/wsdd > *.wsdl > > > exception: > [INFO] Trace > org.apache.maven.reactor.MavenExecutionException: Parse error reading POM > at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:359) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:276) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:113) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:249) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. > java:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces > sorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:324) > 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.project.InvalidProjectModelException: Parse error > re > ading POM > at > org.apache.maven.project.DefaultMavenProjectBuilder.readModel(Default > MavenProjectBuilder.java:1097) > at > org.apache.maven.project.DefaultMavenProjectBuilder.readModel(Default > MavenProjectBuilder.java:1057) > at > org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFi > le(DefaultMavenProjectBuilder.java:291) > at > org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMave > nProjectBuilder.java:276) > at org.apache.maven.DefaultMaven.getProject(DefaultMaven.java:509) > at > org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:441) > at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:345) > ... 11 more > Caused by: org.codehaus.plexus.util.xml.pull.XmlPullParserException: expected > ST > ART_TAG or END_TAG not TEXT (position: TEXT seen ...\r\n > ludes>*.wsdl at > org.codehaus.plexus.util.xml.pull.MXParser.nextTag(MXParser.java:1080 > ) > at > org.apache.maven.model.io.xpp3.MavenXpp3Reader.parseResource(MavenXpp > 3Reader.java:3825) > at > org.apache.maven.model.io.xpp3.MavenXpp3Reader.parseBuild(MavenXpp3Re > ader.java:621) > at > org.apache.maven.model.io.xpp3.MavenXpp3Reader.parseModel(MavenXpp3Re > ader.java:2131) > at > org.apache.maven.model.io.xpp3.MavenXpp3Reader.read(MavenXpp3Reader.j > ava:4255) > at > org.apache.maven.project.DefaultMavenProjectBuilder.readModel(Default > MavenProjectBuilder.java:1093) -- 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] Moved: (DOXIASITETOOLS-1) Provide a schema for site.xml
[ http://jira.codehaus.org/browse/DOXIASITETOOLS-1?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg moved MSITE-118 to DOXIASITETOOLS-1: Affects Version/s: (was: 2.0-beta-5) 1.0-alpha-9 Fix Version/s: (was: 2.0-beta-7) 1.0-beta-1 Component/s: (was: site descriptor) Decoration model Issue Type: Improvement (was: Wish) Key: DOXIASITETOOLS-1 (was: MSITE-118) Project: Maven Doxia Site Tools (was: Maven 2.x Site Plugin) > Provide a schema for site.xml > - > > Key: DOXIASITETOOLS-1 > URL: http://jira.codehaus.org/browse/DOXIASITETOOLS-1 > Project: Maven Doxia Site Tools > Issue Type: Improvement > Components: Decoration model >Affects Versions: 1.0-alpha-9 >Reporter: Wendy Smoak >Assignee: Dennis Lundberg >Priority: Minor > Fix For: 1.0-beta-1 > > > Brett mentioned that a schema for site.xml will be available with > maven-site-plugin 2.0 final. Just logging a reminder issue as I don't see it > in svn or at http://maven.apache.org/xsd/ . > http://mail-archives.apache.org/mod_mbox/maven-users/200602.mbox/[EMAIL > PROTECTED] -- 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] Moved: (DOXIASITETOOLS-3) Add titles to hrefs, tweaks to powered by
[ http://jira.codehaus.org/browse/DOXIASITETOOLS-3?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg moved DOXIA-121 to DOXIASITETOOLS-3: Affects Version/s: (was: 1.0-alpha-8) 1.0-alpha-9 Fix Version/s: (was: 1.0-beta-1) Component/s: (was: Site Renderer) Site renderer Key: DOXIASITETOOLS-3 (was: DOXIA-121) Project: Maven Doxia Site Tools (was: Maven Doxia) > Add titles to hrefs, tweaks to powered by > -- > > Key: DOXIASITETOOLS-3 > URL: http://jira.codehaus.org/browse/DOXIASITETOOLS-3 > Project: Maven Doxia Site Tools > Issue Type: Improvement > Components: Site renderer >Affects Versions: 1.0-alpha-9 > Environment: Firefox/WinXP >Reporter: Tim Pizey >Priority: Trivial > Attachments: default-site.patch > > > Add title to banner images, use div not span tags, add else conditions to > macros, to fix missing version bug, add size and class to poweredby -- 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] Moved: (DOXIASITETOOLS-2) Doxia default site renderer redefines local macros over and over again
[ http://jira.codehaus.org/browse/DOXIASITETOOLS-2?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg moved DOXIA-82 to DOXIASITETOOLS-2: --- Fix Version/s: (was: 1.0) Component/s: (was: Site Renderer) Site renderer Key: DOXIASITETOOLS-2 (was: DOXIA-82) Project: Maven Doxia Site Tools (was: Maven Doxia) > Doxia default site renderer redefines local macros over and over again > -- > > Key: DOXIASITETOOLS-2 > URL: http://jira.codehaus.org/browse/DOXIASITETOOLS-2 > Project: Maven Doxia Site Tools > Issue Type: Bug > Components: Site renderer >Reporter: Henning Schmiedehausen > > The Doxia default site renderer uses Apache Velocity to render its pages. > Every time a page is rendered, Doxia tries to define Velocity Macros but the > Plexus Velocity component sets the replacement of Velocity Macro to false > (the default). > In Velocity Version 1.4, these error messages are silently discarded. In > newer Versions (1.5 beta 2 and beyond), these messages are logged out and > appear to be errors. -- 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: (MSITE-206) Move the webapp features to a separate plugin
[ http://jira.codehaus.org/browse/MSITE-206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg updated MSITE-206: -- Fix Version/s: (was: 2.0-beta-6) 2.0-beta-7 > Move the webapp features to a separate plugin > - > > Key: MSITE-206 > URL: http://jira.codehaus.org/browse/MSITE-206 > Project: Maven 2.x Site Plugin > Issue Type: Improvement > Components: site:run >Affects Versions: 2.0-beta-5 >Reporter: Jason van Zyl >Assignee: Jason van Zyl > Fix For: 2.0-beta-7 > > > Prevent the complete download of Jetty for rendering the site and move to a > separate plugin. -- 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: (DOXIASITETOOLS-3) Add titles to hrefs, tweaks to powered by
[ http://jira.codehaus.org/browse/DOXIASITETOOLS-3?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg updated DOXIASITETOOLS-3: - Fix Version/s: 1.0-beta-1 > Add titles to hrefs, tweaks to powered by > -- > > Key: DOXIASITETOOLS-3 > URL: http://jira.codehaus.org/browse/DOXIASITETOOLS-3 > Project: Maven Doxia Site Tools > Issue Type: Improvement > Components: Site renderer >Affects Versions: 1.0-alpha-9 > Environment: Firefox/WinXP >Reporter: Tim Pizey >Priority: Trivial > Fix For: 1.0-beta-1 > > Attachments: default-site.patch > > > Add title to banner images, use div not span tags, add else conditions to > macros, to fix missing version bug, add size and class to poweredby -- 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: (DOXIASITETOOLS-2) Doxia default site renderer redefines local macros over and over again
[ http://jira.codehaus.org/browse/DOXIASITETOOLS-2?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg updated DOXIASITETOOLS-2: - Fix Version/s: 1.0 > Doxia default site renderer redefines local macros over and over again > -- > > Key: DOXIASITETOOLS-2 > URL: http://jira.codehaus.org/browse/DOXIASITETOOLS-2 > Project: Maven Doxia Site Tools > Issue Type: Bug > Components: Site renderer >Reporter: Henning Schmiedehausen > Fix For: 1.0 > > > The Doxia default site renderer uses Apache Velocity to render its pages. > Every time a page is rendered, Doxia tries to define Velocity Macros but the > Plexus Velocity component sets the replacement of Velocity Macro to false > (the default). > In Velocity Version 1.4, these error messages are silently discarded. In > newer Versions (1.5 beta 2 and beyond), these messages are logged out and > appear to be errors. -- 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: (MSITE-251) tr locale support
[ http://jira.codehaus.org/browse/MSITE-251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_106850 ] Dennis Lundberg commented on MSITE-251: --- We are approaching the time to cut the next release. If you want to get this translation into that release, please respond here. > tr locale support > - > > Key: MSITE-251 > URL: http://jira.codehaus.org/browse/MSITE-251 > Project: Maven 2.x Site Plugin > Issue Type: New Feature > Components: localization > Environment: Windows XP >Reporter: gulcan yalcinkaya >Priority: Trivial > Attachments: project-info-report_tr.properties, > site-plugin_tr.properties > > -- 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: (MSITE-212) Catalan Language
[ http://jira.codehaus.org/browse/MSITE-212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_106849 ] Dennis Lundberg commented on MSITE-212: --- We are approaching the time to cut the next release. If you want to get this translation into that release, please respond here. > Catalan Language > > > Key: MSITE-212 > URL: http://jira.codehaus.org/browse/MSITE-212 > Project: Maven 2.x Site Plugin > Issue Type: New Feature > Components: localization >Reporter: Javier de Ros > Attachments: site-plugin_ca.properties > > > That's the Catalan language properties for the maven site plugin. -- 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] Closed: (MNG-1985) Triggering Profiles bugs
[ http://jira.codehaus.org/browse/MNG-1985?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter closed MNG-1985. - Resolution: Won't Fix > Triggering Profiles bugs > > > Key: MNG-1985 > URL: http://jira.codehaus.org/browse/MNG-1985 > Project: Maven 2 > Issue Type: Bug > Components: Profiles >Affects Versions: 2.0.2 > Environment: windows2000 maven 2.02 >Reporter: pinghe >Priority: Critical > Fix For: 2.0.x > > > ===env 1, > inside pom.xml > > > env-common > > true > > > > os-win32 > > true > > > performRelease > > > > > env-prod > > > performRelease > > > > > exec: mvn projecthelp:active-profiles > output: > - env-common (source: pom) > - os-win32 (source: pom) > exec: mvn projecthelp:active-profiles -DperformRelease > output: > - env-prod (source: pom) > - os-win32 (source: pom) > expect: > - env-prod (source: pom) > - os-win32 (source: pom) > - env-common (source: pom) > ===env 2: > inside pom.xml > > > env-common > > true > > > > os-win32 > > true > > windows > > > performRelease > > > > > env-prod > > > performRelease > > > > > exec: mvn projecthelp:active-profiles > output: > - os-win32 (source: pom) > expect: > - env-prod (source: pom) > - os-win32 (source: pom) -- 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] Closed: (MNG-2294) If /project/parent/relativePath fails to resolve, no error is reported.
[ http://jira.codehaus.org/browse/MNG-2294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter closed MNG-2294. - Resolution: Won't Fix > If /project/parent/relativePath fails to resolve, no error is reported. > --- > > Key: MNG-2294 > URL: http://jira.codehaus.org/browse/MNG-2294 > Project: Maven 2 > Issue Type: Bug > Components: Logging >Affects Versions: 2.0.4 >Reporter: David Smiley >Assignee: Maria Odea Ching > Fix For: 2.0.x > > Original Estimate: 15 hours > Remaining Estimate: 15 hours > > If I have a bad /project/parent/relativePath specified, maven does not tell > me. Instead the build proceeds as if there is no parent. The build should > fail if the parent can't be resolved. -- 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: (MNG-2294) If /project/parent/relativePath fails to resolve, no error is reported.
[ http://jira.codehaus.org/browse/MNG-2294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter reopened MNG-2294: --- > If /project/parent/relativePath fails to resolve, no error is reported. > --- > > Key: MNG-2294 > URL: http://jira.codehaus.org/browse/MNG-2294 > Project: Maven 2 > Issue Type: Bug > Components: Logging >Affects Versions: 2.0.4 >Reporter: David Smiley >Assignee: Maria Odea Ching > Fix For: 2.0.x > > Original Estimate: 15 hours > Remaining Estimate: 15 hours > > If I have a bad /project/parent/relativePath specified, maven does not tell > me. Instead the build proceeds as if there is no parent. The build should > fail if the parent can't be resolved. -- 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: (MNG-1985) Triggering Profiles bugs
[ http://jira.codehaus.org/browse/MNG-1985?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter reopened MNG-1985: --- > Triggering Profiles bugs > > > Key: MNG-1985 > URL: http://jira.codehaus.org/browse/MNG-1985 > Project: Maven 2 > Issue Type: Bug > Components: Profiles >Affects Versions: 2.0.2 > Environment: windows2000 maven 2.02 >Reporter: pinghe >Priority: Critical > Fix For: 2.0.x > > > ===env 1, > inside pom.xml > > > env-common > > true > > > > os-win32 > > true > > > performRelease > > > > > env-prod > > > performRelease > > > > > exec: mvn projecthelp:active-profiles > output: > - env-common (source: pom) > - os-win32 (source: pom) > exec: mvn projecthelp:active-profiles -DperformRelease > output: > - env-prod (source: pom) > - os-win32 (source: pom) > expect: > - env-prod (source: pom) > - os-win32 (source: pom) > - env-common (source: pom) > ===env 2: > inside pom.xml > > > env-common > > true > > > > os-win32 > > true > > windows > > > performRelease > > > > > env-prod > > > performRelease > > > > > exec: mvn projecthelp:active-profiles > output: > - os-win32 (source: pom) > expect: > - env-prod (source: pom) > - os-win32 (source: pom) -- 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-1038) Build definitions should list what type they are (ant, maven, maven2, shell)
[ http://jira.codehaus.org/browse/CONTINUUM-1038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_106853 ] Olivier Lamy commented on CONTINUUM-1038: - This require a db change to store the type. As we already have a db change for 1.1-beta-3 (CONTINUUM-1427) in Builddefinition, I will add an other field (java field type sql colunm executor_type). > Build definitions should list what type they are (ant, maven, maven2, shell) > > > Key: CONTINUUM-1038 > URL: http://jira.codehaus.org/browse/CONTINUUM-1038 > Project: Continuum > Issue Type: Bug > Components: Web - UI >Affects Versions: 1.1-alpha-1 >Reporter: Brett Porter >Assignee: Olivier Lamy > Fix For: 1.1-beta-3 > > -- 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: (MNG-2730) useful developer bash functions for Maven
[ http://jira.codehaus.org/browse/MNG-2730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated MNG-2730: -- Attachment: mvn_functions_bashrc.txt updated for apache-maven-* naming > useful developer bash functions for Maven > - > > Key: MNG-2730 > URL: http://jira.codehaus.org/browse/MNG-2730 > Project: Maven 2 > Issue Type: New Feature > Components: Documentation: General >Reporter: Brett Porter > Fix For: Documentation Deficit > > Attachments: mvn_functions_bashrc.txt, mvn_functions_bashrc.txt, > mvn_functions_bashrc.txt > > > useful bash functions. We could include this in the dev section of the web > site -- 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-1710) gwt-widgets-0.1.5
gwt-widgets-0.1.5 - Key: MAVENUPLOAD-1710 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1710 Project: maven-upload-requests Issue Type: Task Reporter: Ryan Heaton The GWT Widget Library is a set of enhancements and utilities for the Google Web Toolkit client-side code. -- 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-1710) gwt-widgets-0.1.5
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_106856 ] Ryan Heaton commented on MAVENUPLOAD-1710: -- I'm not a developer, but I'm anxious to have these libraries available via the m2 repo. I'm planning a release of Enunciate that depends on these libs. If permission is needed from the project owner please confirm with [iamroberthanson at users.sourceforge.net]. > gwt-widgets-0.1.5 > - > > Key: MAVENUPLOAD-1710 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1710 > Project: maven-upload-requests > Issue Type: Task >Reporter: Ryan Heaton > > The GWT Widget Library is a set of enhancements and utilities for the Google > Web Toolkit client-side code. -- 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-1711) gwt-widgets-server-0.1.4
gwt-widgets-server-0.1.4 Key: MAVENUPLOAD-1711 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1711 Project: maven-upload-requests Issue Type: Task Reporter: Ryan Heaton The GWT Widget Server Library is a collection of server-side components for the Google Web Toolkit facilitating publishing of Spring beans as RPC services. -- 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-1711) gwt-widgets-server-0.1.4
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_106857 ] Ryan Heaton commented on MAVENUPLOAD-1711: -- I'm not a developer, but I'm anxious to have these libraries available via the m2 repo. I'm planning a release of Enunciate that depends on these libs. If permission is needed from the project owner please confirm with [iamroberthanson at users.sourceforge.net]. > gwt-widgets-server-0.1.4 > > > Key: MAVENUPLOAD-1711 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1711 > Project: maven-upload-requests > Issue Type: Task >Reporter: Ryan Heaton > > The GWT Widget Server Library is a collection of server-side components for > the Google Web Toolkit facilitating publishing of Spring beans as RPC > services. -- 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
