No, the codehaus jira. So, will use the new one :-) 2011/3/22 Rene Groeschke <[email protected]>
> Hi, > did you use the new jira instance available at > http://issues.gradle.orginstead of the codehaus jira? > > regards, > René > > Am 22.03.11 23:12, schrieb Sten Roger Sandvik: > > I logged into jira but it does not seem that I can create an issue here. > Cannot find the gradle project (GRADLE) in project list. I can see the > status and all issues, but cannot find the project in "create new issue" > dialog. So, cannot add issue at this moment. Any clues? > > 2011/3/22 Adam Murdoch <[email protected]> > >> >> On 23/03/2011, at 8:56 AM, Sten Roger Sandvik wrote: >> >> Yes, I can add a jira issue. Should'nt the zip task variants be safe so >> that it does not add multiple entries with the same name? >> >> >> By default, yes. That would be the solution to the problem. Plus we'd >> also need to make sure the correct manifest.mf got included, so it's also >> about ordering things correctly. >> >> >> >> 2011/3/22 Adam Murdoch <[email protected]> >> >>> >>> On 23/03/2011, at 8:00 AM, Sten Roger Sandvik wrote: >>> >>> >>> That worked, but I get two META-INF/MANIFEST.MF entries in the war file. >>> >>> >>> Could you add a jira issue for this problem? >>> >>> >>> Is it possible to filter out non-unique files? >>> >>> >>> A work around is: >>> >>> war { >>> into("/") { >>> exclude 'META-INF/MANIFEST.MF' // or whatever >>> with project(':common').war >>> } >>> } >>> >>> >>> >>> 2011/3/22 Adam Murdoch <[email protected]> >>> >>>> Or, if the commons project uses the war plugin, you can do something >>>> like this: >>>> >>>> war { >>>> with project(':commons').war >>>> } >>>> >>>> This will pick up the convention stuff above, plus any customisations >>>> done to the contents of the war in the commons project. >>>> >>>> >>>> >>>> -- >>>> Peter Niederwieser >>>> Developer, Gradle >>>> http://www.gradle.org >>>> Trainer & Consultant, Gradleware >>>> http://www.gradleware.com >>>> Creator, Spock Framework >>>> http://spockframework.org >>>> >>>> >>>> >>>> Sten Roger Sandvik-2 wrote: >>>> >>>> >>>> Well, Maven uses something they call WebApp overlays. It's not great, >>>> but >>>> >>>> it >>>> >>>> works. At least for small projects :-) What I want Gradle to do is the >>>> >>>> following: >>>> >>>> >>>> * Common webapp project builds as usual (no magic stuff here) >>>> >>>> * Specialized webapp has sourceSets to itself and to the common >>>> webapp. >>>> >>>> * Specialized webapp has dependencies from common webapp and >>>> additional >>>> >>>> dependencies. >>>> >>>> * Specialized webapp adds common webapp compiled classes/resources and >>>> >>>> it's own compiled classes/resources. >>>> >>>> >>>> Anyone have done something like this? >>>> >>>> >>>> >>>> -- >>>> View this message in context: >>>> http://gradle.1045684.n5.nabble.com/War-dependency-to-another-war-tp4257270p4257485.html >>>> Sent from the gradle-user mailing list archive at Nabble.com. >>>> >>>> --------------------------------------------------------------------- >>>> To unsubscribe from this list, please visit: >>>> >>>> http://xircles.codehaus.org/manage_email >>>> >>>> >>>> >>>> >>>> -- >>>> Adam Murdoch >>>> Gradle Developer >>>> http://www.gradle.org >>>> Co-Founder and VP of Engineering, Gradleware Inc. - Gradle Training, >>>> Support, Consulting >>>> http://www.gradleware.com >>>> >>>> >>> >>> >>> -- >>> Adam Murdoch >>> Gradle Developer >>> http://www.gradle.org >>> Co-Founder and VP of Engineering, Gradleware Inc. - Gradle Training, >>> Support, Consulting >>> http://www.gradleware.com >>> >>> >> >> >> -- >> Adam Murdoch >> Gradle Developer >> http://www.gradle.org >> Co-Founder and VP of Engineering, Gradleware Inc. - Gradle Training, >> Support, Consulting >> http://www.gradleware.com >> >> > > > -- > ----------------------- > regards René > > rene groeschkehttp://www.breskeby.com > @breskeby > >
