[JBoss JIRA] (JBIDE-16309) Move inter-JBT dependencies to component poms
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16309?page=com.atlassian.jira.plugi... ]
Mickael Istria updated JBIDE-16309:
-----------------------------------
Git Pull Request: https://github.com/jbosstools/jbosstools-build/pull/131, https://github.com/jbosstools/jbosstools-javaee/pull/186, https://github.com/jbosstools/jbosstools-jst/pull/248, https://github.com/jbosstools/jbosstools-arquillian/pull/50, https://github.com/jbosstools/jbosstools-central/pull/201, https://github.com/jbosstools/jbosstools-hibernate/pull/35, https://github.com/jbosstools/jbosstools-livereload/pull/70, https://github.com/jbosstools/jbosstools-openshift/pull/344 (was: https://github.com/jbosstools/jbosstools-build/pull/131, https://github.com/jbosstools/jbosstools-javaee/pull/186, https://github.com/jbosstools/jbosstools-jst/pull/248, https://github.com/jbosstools/jbosstools-arquillian/pull/50, https://github.com/jbosstools/jbosstools-central/pull/201, https://github.com/jbosstools/jbosstools-hibernate/pull/35, https://github.com/jbosstools/jbosstools-livereload/pull/70)
> Move inter-JBT dependencies to component poms
> ---------------------------------------------
>
> Key: JBIDE-16309
> URL: https://issues.jboss.org/browse/JBIDE-16309
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: build
> Reporter: Mickael Istria
> Assignee: Mickael Istria
> Fix For: 4.2.0.Alpha2
>
>
> It has been discussed several times that the composite site is a kind of "weak point" in our build chain, because it allows cyclic dependencies, and it also introduces indirections that make it less straightforward to find out what a project should/does depend on to build.
> The benefit of composite now seem a bit light: it's cool because we can put it in parent pom and all builds succeed to get there dependencies, but out of that, there hasn't been much other use-cases. And as we want to provide more and more autonomy to project, this composite site they'd depend on is something that doesn't make them autonomous.
> So the idea is to move dependencies to project root poms. I've made a draft of how it would look like in project pom if we remove the "jbosstools-site" from parent pom and let projects manage their inter-dependencies: https://github.com/mickaelistria/jbosstools-javaee/tree/JBIDE-16309
> You can try this by running "mvn clean verify -P\!jbosstools-site". The "-P\!jbosstools-site" disable the jbosstools-site profile, which is the one controlling addition of the composite or ggregate to the resolver
> https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.xml...
--
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
12 years, 7 months
[JBoss JIRA] (JBIDE-16309) Move inter-JBT dependencies to component poms
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16309?page=com.atlassian.jira.plugi... ]
Mickael Istria updated JBIDE-16309:
-----------------------------------
Git Pull Request: https://github.com/jbosstools/jbosstools-build/pull/131, https://github.com/jbosstools/jbosstools-javaee/pull/186, https://github.com/jbosstools/jbosstools-jst/pull/248, https://github.com/jbosstools/jbosstools-arquillian/pull/50, https://github.com/jbosstools/jbosstools-central/pull/201, https://github.com/jbosstools/jbosstools-hibernate/pull/35, https://github.com/jbosstools/jbosstools-livereload/pull/70 (was: https://github.com/jbosstools/jbosstools-build/pull/131, https://github.com/jbosstools/jbosstools-javaee/pull/186, https://github.com/jbosstools/jbosstools-jst/pull/248, https://github.com/jbosstools/jbosstools-arquillian/pull/50, https://github.com/jbosstools/jbosstools-central/pull/201, https://github.com/jbosstools/jbosstools-hibernate/pull/35)
> Move inter-JBT dependencies to component poms
> ---------------------------------------------
>
> Key: JBIDE-16309
> URL: https://issues.jboss.org/browse/JBIDE-16309
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: build
> Reporter: Mickael Istria
> Assignee: Mickael Istria
> Fix For: 4.2.0.Alpha2
>
>
> It has been discussed several times that the composite site is a kind of "weak point" in our build chain, because it allows cyclic dependencies, and it also introduces indirections that make it less straightforward to find out what a project should/does depend on to build.
> The benefit of composite now seem a bit light: it's cool because we can put it in parent pom and all builds succeed to get there dependencies, but out of that, there hasn't been much other use-cases. And as we want to provide more and more autonomy to project, this composite site they'd depend on is something that doesn't make them autonomous.
> So the idea is to move dependencies to project root poms. I've made a draft of how it would look like in project pom if we remove the "jbosstools-site" from parent pom and let projects manage their inter-dependencies: https://github.com/mickaelistria/jbosstools-javaee/tree/JBIDE-16309
> You can try this by running "mvn clean verify -P\!jbosstools-site". The "-P\!jbosstools-site" disable the jbosstools-site profile, which is the one controlling addition of the composite or ggregate to the resolver
> https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.xml...
--
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
12 years, 7 months
[JBoss JIRA] (JBIDE-16128) Publish component sites to Nexus
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16128?page=com.atlassian.jira.plugi... ]
Mickael Istria updated JBIDE-16128:
-----------------------------------
Fix Version/s: 4.2.0.Beta1
(was: 4.2.0.Alpha2)
> Publish component sites to Nexus
> --------------------------------
>
> Key: JBIDE-16128
> URL: https://issues.jboss.org/browse/JBIDE-16128
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: build
> Reporter: Mickael Istria
> Assignee: Mickael Istria
> Fix For: 4.2.0.Beta1
>
> Attachments: deployWithJenkins.png
>
>
> In order to get a first idea of how easy/difficult it would be to rely on Nexus for publication,we could simply start by configuring CI jobs to also run a "mvn deploy" to deploy the output p2 repository onto Nexus.
> Then we'll see what are the pros/cons of this approach.
> Current publication process and locations will be kept. These p2 repo on Nexus won't be consumed by aggregator, at least not until we are sure it's worth it.
--
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
12 years, 7 months
[JBoss JIRA] (JBIDE-16309) Move inter-JBT dependencies to component poms
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16309?page=com.atlassian.jira.plugi... ]
Mickael Istria updated JBIDE-16309:
-----------------------------------
Git Pull Request: https://github.com/jbosstools/jbosstools-build/pull/131, https://github.com/jbosstools/jbosstools-javaee/pull/186, https://github.com/jbosstools/jbosstools-jst/pull/248, https://github.com/jbosstools/jbosstools-arquillian/pull/50, https://github.com/jbosstools/jbosstools-central/pull/201, https://github.com/jbosstools/jbosstools-hibernate/pull/35 (was: https://github.com/jbosstools/jbosstools-build/pull/131, https://github.com/jbosstools/jbosstools-javaee/pull/186, https://github.com/jbosstools/jbosstools-jst/pull/248, https://github.com/jbosstools/jbosstools-arquillian/pull/50, https://github.com/jbosstools/jbosstools-central/pull/201)
> Move inter-JBT dependencies to component poms
> ---------------------------------------------
>
> Key: JBIDE-16309
> URL: https://issues.jboss.org/browse/JBIDE-16309
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: build
> Reporter: Mickael Istria
> Assignee: Mickael Istria
> Fix For: 4.2.0.Alpha2
>
>
> It has been discussed several times that the composite site is a kind of "weak point" in our build chain, because it allows cyclic dependencies, and it also introduces indirections that make it less straightforward to find out what a project should/does depend on to build.
> The benefit of composite now seem a bit light: it's cool because we can put it in parent pom and all builds succeed to get there dependencies, but out of that, there hasn't been much other use-cases. And as we want to provide more and more autonomy to project, this composite site they'd depend on is something that doesn't make them autonomous.
> So the idea is to move dependencies to project root poms. I've made a draft of how it would look like in project pom if we remove the "jbosstools-site" from parent pom and let projects manage their inter-dependencies: https://github.com/mickaelistria/jbosstools-javaee/tree/JBIDE-16309
> You can try this by running "mvn clean verify -P\!jbosstools-site". The "-P\!jbosstools-site" disable the jbosstools-site profile, which is the one controlling addition of the composite or ggregate to the resolver
> https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.xml...
--
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
12 years, 7 months
[JBoss JIRA] (JBIDE-16309) Move inter-JBT dependencies to component poms
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16309?page=com.atlassian.jira.plugi... ]
Mickael Istria updated JBIDE-16309:
-----------------------------------
Git Pull Request: https://github.com/jbosstools/jbosstools-build/pull/131, https://github.com/jbosstools/jbosstools-javaee/pull/186, https://github.com/jbosstools/jbosstools-jst/pull/248, https://github.com/jbosstools/jbosstools-arquillian/pull/50, https://github.com/jbosstools/jbosstools-central/pull/201 (was: https://github.com/jbosstools/jbosstools-build/pull/131, https://github.com/jbosstools/jbosstools-javaee/pull/186, https://github.com/jbosstools/jbosstools-jst/pull/248, https://github.com/jbosstools/jbosstools-arquillian/pull/50)
> Move inter-JBT dependencies to component poms
> ---------------------------------------------
>
> Key: JBIDE-16309
> URL: https://issues.jboss.org/browse/JBIDE-16309
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: build
> Reporter: Mickael Istria
> Assignee: Mickael Istria
> Fix For: 4.2.0.Alpha2
>
>
> It has been discussed several times that the composite site is a kind of "weak point" in our build chain, because it allows cyclic dependencies, and it also introduces indirections that make it less straightforward to find out what a project should/does depend on to build.
> The benefit of composite now seem a bit light: it's cool because we can put it in parent pom and all builds succeed to get there dependencies, but out of that, there hasn't been much other use-cases. And as we want to provide more and more autonomy to project, this composite site they'd depend on is something that doesn't make them autonomous.
> So the idea is to move dependencies to project root poms. I've made a draft of how it would look like in project pom if we remove the "jbosstools-site" from parent pom and let projects manage their inter-dependencies: https://github.com/mickaelistria/jbosstools-javaee/tree/JBIDE-16309
> You can try this by running "mvn clean verify -P\!jbosstools-site". The "-P\!jbosstools-site" disable the jbosstools-site profile, which is the one controlling addition of the composite or ggregate to the resolver
> https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.xml...
--
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
12 years, 7 months
[JBoss JIRA] (JBIDE-16356) OpenShift project wizard does not handle a dirty/modified git project gracefully
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16356?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-16356:
---------------------------------------------
I agree with [~adietish] analysis. This is caused by you trying to import a subproject of another gitrepo into openshift.
That won't "just work" in many if not all cases since openshift itself assumes the root project has a certain directory layout.
Best thing we can do is probably detect this and warn the user this project is not possible to import before you take it out of your exisitng git clone.
Or we'll need to tell the user if okey we copy the content into yet another new project.
> OpenShift project wizard does not handle a dirty/modified git project gracefully
> --------------------------------------------------------------------------------
>
> Key: JBIDE-16356
> URL: https://issues.jboss.org/browse/JBIDE-16356
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Reporter: Burr Sutter
> Attachments: contacts-mobile-basic.zip
>
>
> I am getting an odd error message.
> Here are the steps:
> 1) git clone https://github.com/joshuawilson/jboss-wfk-quickstarts.git
> 2) git checkout WFK-113
> 3) JBDS 7.1 import as Maven project
> 4) tweak the pom.xml (it was broken but now fixed)
> 5) it deploys to a local EAP, now attempt to send to OpenShift
> 6) run the OpenShift wizard as seen in the video
> http://screencast.com/t/NVTPK4pL
--
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
12 years, 7 months
[JBoss JIRA] (JBIDE-16355) replace release_notes*.html files posted to sourceforge w/ link directly to JIRA query
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16355?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-16355:
---------------------------------------------
[~nickboldt] how is that different from the link I sent which is the stable and simpler url ?
afaics they are exactly the same, except https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=10020&version=... is simpler?
what am I missing ?
> replace release_notes*.html files posted to sourceforge w/ link directly to JIRA query
> --------------------------------------------------------------------------------------
>
> Key: JBIDE-16355
> URL: https://issues.jboss.org/browse/JBIDE-16355
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.2.0.Alpha2
> Reporter: Nick Boldt
> Assignee: Mickael Istria
>
> Re: files like:
> http://sourceforge.net/projects/jboss/files/JBossTools/JBossTools4.2.0.x/...
> {quote}
> (2014-01-14 13:55:54) nickboldt: desire to produce the file is clearly no longer urgent, so I could open a JIRA asking to trash it from the rel guide requirement for JBT 4.2 and see who disagrees
> (2014-01-14 13:56:04) maxandersen: yeah - and I keep saying: please dont use mixed camelcases but they keep occuring ;)
> (2014-01-14 13:56:25) maxandersen: yeah I would just post a jira query IMO for these.
> (2014-01-14 13:56:56) maxandersen: dont use mixed camelcases for artifacts urls I mean.
> (2014-01-14 13:57:58) maxandersen: interesting - *1* hit on google for jbide zz_release_notes ;)
> (2014-01-14 13:58:34) maxandersen: so yeah, jira query ftw for this.
> {quote}
> Instead of producing a snapshot from JIRA as a canned HTML page, we should for JBT 4.2 / JBDS 8 simply link to a query.
> That way too we can have a query for "just this milestone" and "all changes in the 4.2.x stream (alpha1, alpha2, beta1, cr1, final).
> We can also produce a query for both JBT and JBDS.
--
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
12 years, 7 months
[JBoss JIRA] (JBIDE-16370) evaluate creating OSGi bindex
by Mickael Istria (JIRA)
Mickael Istria created JBIDE-16370:
--------------------------------------
Summary: evaluate creating OSGi bindex
Key: JBIDE-16370
URL: https://issues.jboss.org/browse/JBIDE-16370
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: build, locus
Environment: Since it is easy to create OSGi bindex (equivalent of p2, but specified by OSGi standard, works outside of Eclipse) using https://github.com/bndtools/bindex , it would be nice to include those bindex in the p2 repo we deliver to support standards as well.
Reporter: Mickael Istria
Priority: Optional
--
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
12 years, 7 months
[JBoss JIRA] (JBIDE-16309) Move inter-JBT dependencies to component poms
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16309?page=com.atlassian.jira.plugi... ]
Mickael Istria updated JBIDE-16309:
-----------------------------------
Git Pull Request: https://github.com/jbosstools/jbosstools-build/pull/131, https://github.com/jbosstools/jbosstools-javaee/pull/186, https://github.com/jbosstools/jbosstools-jst/pull/248, https://github.com/jbosstools/jbosstools-arquillian/pull/50 (was: https://github.com/jbosstools/jbosstools-build/pull/131, https://github.com/jbosstools/jbosstools-javaee/pull/186, https://github.com/jbosstools/jbosstools-jst/pull/248)
> Move inter-JBT dependencies to component poms
> ---------------------------------------------
>
> Key: JBIDE-16309
> URL: https://issues.jboss.org/browse/JBIDE-16309
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: build
> Reporter: Mickael Istria
> Assignee: Mickael Istria
> Fix For: 4.2.0.Alpha2
>
>
> It has been discussed several times that the composite site is a kind of "weak point" in our build chain, because it allows cyclic dependencies, and it also introduces indirections that make it less straightforward to find out what a project should/does depend on to build.
> The benefit of composite now seem a bit light: it's cool because we can put it in parent pom and all builds succeed to get there dependencies, but out of that, there hasn't been much other use-cases. And as we want to provide more and more autonomy to project, this composite site they'd depend on is something that doesn't make them autonomous.
> So the idea is to move dependencies to project root poms. I've made a draft of how it would look like in project pom if we remove the "jbosstools-site" from parent pom and let projects manage their inter-dependencies: https://github.com/mickaelistria/jbosstools-javaee/tree/JBIDE-16309
> You can try this by running "mvn clean verify -P\!jbosstools-site". The "-P\!jbosstools-site" disable the jbosstools-site profile, which is the one controlling addition of the composite or ggregate to the resolver
> https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.xml...
--
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
12 years, 7 months