[JBoss JIRA] (JBIDE-12815) Create a JBoss Tools Orbit
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12815?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-12815:
------------------------------------
BTW, https://github.com/reficio/p2-maven-plugin is a non-starter as it does not appear to have a way to change the Bundle-SymbolicName from "poi" to "org.jboss.tools.locus.apache.poi" and it won't allow multiple jars (or their *.class contents) to be merged into a single osgi jar.
> Create a JBoss Tools Orbit
> --------------------------
>
> Key: JBIDE-12815
> URL: https://issues.jboss.org/browse/JBIDE-12815
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: Build/Releng, locus
> Reporter: Mickael Istria
> Assignee: Max Rydahl Andersen
> Fix For: 4.1.0.Beta1
>
> Attachments: pom.xml
>
>
> Since all JBoss Eclipse-based project probably share some needs for usual libraries, we should create a JBoss Tools Orbit project in which one we would provide those 3rd-party dependencies packaged as OSGi Bundle in a p2 repository.
> In a first time, we could simply create some OSGi "wrappers" around those jars.
--
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, 11 months
[JBoss JIRA] (JBIDE-12815) Create a JBoss Tools Orbit
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12815?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-12815:
-------------------------------
Attachment: pom.xml
> Create a JBoss Tools Orbit
> --------------------------
>
> Key: JBIDE-12815
> URL: https://issues.jboss.org/browse/JBIDE-12815
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: Build/Releng, locus
> Reporter: Mickael Istria
> Assignee: Max Rydahl Andersen
> Fix For: 4.1.0.Beta1
>
> Attachments: pom.xml
>
>
> Since all JBoss Eclipse-based project probably share some needs for usual libraries, we should create a JBoss Tools Orbit project in which one we would provide those 3rd-party dependencies packaged as OSGi Bundle in a p2 repository.
> In a first time, we could simply create some OSGi "wrappers" around those jars.
--
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, 11 months
[JBoss JIRA] (JBDS-2534) JBDS70_0311: [Commit] (Dev) (P2) Marketplace - simplify delivery
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-2534?page=com.atlassian.jira.plugin.... ]
Nick Boldt edited comment on JBDS-2534 at 5/8/13 11:07 AM:
-----------------------------------------------------------
[~maxandersen] If you don't like the term "Tech Preview", then we can call it "Incubator" instead.
If the goal is to have JBDS on the marketplace + an incubator for non-JBDS stuff, why not do that now, for Beta1? Either way, I'm being asked to create a second Marketplace entry.
Only difference is that I'd be creating a new pair of jobs (_master, _41) for a new JBT Incubator site / zip, which is very little effort. And it means that the category.xml files lists of included IUs for the JBT Core (non-incubating) and JBDS sites would be ever closer to being identical (but for differences of categorization / uncategorization).
So I'm all for doing this for JBT 4.1 Beta1 / JBDS 7 Beta1. I don't see a reason to postpone it and slip this PRD request to the next release.
was (Author: nickboldt):
If the goal is to have JBDS on the marketplace + an incubator for non-JBDS stuff, why not do that now, for Beta1? Either way, I'm being asked to create a second Marketplace entry.
Only difference is that I'd be creating a new pair of jobs (_master, _41) for a new JBT Incubator site / zip, which is very little effort. And it means that the category.xml files lists of included IUs for the JBT Core (non-incubating) and JBDS sites would be ever closer to being identical (but for differences of categorization / uncategorization).
So I'm all for doing this for JBT 4.1 Beta1 / JBDS 7 Beta1. I don't see a reason to postpone it and slip this PRD request to the next release.
> JBDS70_0311: [Commit] (Dev) (P2) Marketplace - simplify delivery
> ----------------------------------------------------------------
>
> Key: JBDS-2534
> URL: https://issues.jboss.org/browse/JBDS-2534
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Requirements
> Affects Versions: 7.0.0.GA
> Reporter: Jiri Pallich
> Assignee: Nick Boldt
> Fix For: 7.0.0.Beta1
>
>
> JBDS only on Marketplace (no more JBoss Tools entry).
--
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, 11 months
[JBoss JIRA] (JBDS-2534) JBDS70_0311: [Commit] (Dev) (P2) Marketplace - simplify delivery
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-2534?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-2534:
----------------------------------
If the goal is to have JBDS on the marketplace + an incubator for non-JBDS stuff, why not do that now, for Beta1? Either way, I'm being asked to create a second Marketplace entry.
Only difference is that I'd be creating a new pair of jobs (_master, _41) for a new JBT Incubator site / zip, which is very little effort. And it means that the category.xml files lists of included IUs for the JBT Core (non-incubating) and JBDS sites would be ever closer to being identical (but for differences of categorization / uncategorization).
So I'm all for doing this for JBT 4.1 Beta1 / JBDS 7 Beta1. I don't see a reason to postpone it and slip this PRD request to the next release.
> JBDS70_0311: [Commit] (Dev) (P2) Marketplace - simplify delivery
> ----------------------------------------------------------------
>
> Key: JBDS-2534
> URL: https://issues.jboss.org/browse/JBDS-2534
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Requirements
> Affects Versions: 7.0.0.GA
> Reporter: Jiri Pallich
> Assignee: Nick Boldt
> Fix For: 7.0.0.Beta1
>
>
> JBDS only on Marketplace (no more JBoss Tools entry).
--
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, 11 months
[JBoss JIRA] (JBIDE-12815) Create a JBoss Tools Orbit
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12815?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-12815:
---------------------------------------------
4) there should be no -SNAPSHOT version in these bundles when released/built.
> Create a JBoss Tools Orbit
> --------------------------
>
> Key: JBIDE-12815
> URL: https://issues.jboss.org/browse/JBIDE-12815
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: Build/Releng, locus
> Reporter: Mickael Istria
> Assignee: Max Rydahl Andersen
> Fix For: 4.1.0.Beta1
>
>
> Since all JBoss Eclipse-based project probably share some needs for usual libraries, we should create a JBoss Tools Orbit project in which one we would provide those 3rd-party dependencies packaged as OSGi Bundle in a p2 repository.
> In a first time, we could simply create some OSGi "wrappers" around those jars.
--
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, 11 months
[JBoss JIRA] (JBIDE-12815) Create a JBoss Tools Orbit
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12815?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-12815:
---------------------------------------------
I've finally gotten around to publish my README.md PR at https://github.com/nickboldt/jbosstools-locus/pull/1
This is/was very much based on what is found on Orbit docs about how to do these bundles.
In doing so i've found some discrepencies compared to Orbit we'll need to react to.
1) we are adding jar's inside a bundle instead of using the actual real jar with updated manifest.mf - and advantage/disadvantage to this ?
2) fest contains multiple jar's incl. javadoc jar - that seems wrong. Why is it not one bundle per jar ?
3) Required execution environment is set to java 6 - is that true for all ?
> Create a JBoss Tools Orbit
> --------------------------
>
> Key: JBIDE-12815
> URL: https://issues.jboss.org/browse/JBIDE-12815
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: Build/Releng, locus
> Reporter: Mickael Istria
> Assignee: Max Rydahl Andersen
> Fix For: 4.1.0.Beta1
>
>
> Since all JBoss Eclipse-based project probably share some needs for usual libraries, we should create a JBoss Tools Orbit project in which one we would provide those 3rd-party dependencies packaged as OSGi Bundle in a p2 repository.
> In a first time, we could simply create some OSGi "wrappers" around those jars.
--
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, 11 months
[JBoss JIRA] (JBIDE-14342) I dont get credentials reported when I create a jenkins
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14342?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-14342:
------------------------------------------
for 1) I added a specific message to the creation log dialog. It holds a link to the environment variables so that one can easily go and look the credentials up.
!timouted-see-in-envvars.png!
> I dont get credentials reported when I create a jenkins
> -------------------------------------------------------
>
> Key: JBIDE-14342
> URL: https://issues.jboss.org/browse/JBIDE-14342
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.1.0.Alpha2
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Priority: Critical
> Fix For: 4.1.0.Beta1
>
> Attachments: correct-creation-log.png, no-information-from-openshift.png, null-creation-log.png, timouted-see-in-envvars.png
>
>
--
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, 11 months