[JBoss JIRA] (JBIDE-13232) refactor target platforms' GAVs, names, labels (was target platforms has the same name)
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13232?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-13232:
----------------------------------------
+1 for Nick proposal.
I think if we remove SNAPSHOT, the we only need tags (tags <=> release; branch <=> SNAPSHOT). SNAPSHOT and branch are only useful if we plan to modify the TP after it's published to Nexus.
> refactor target platforms' GAVs, names, labels (was target platforms has the same name)
> ---------------------------------------------------------------------------------------
>
> Key: JBIDE-13232
> URL: https://issues.jboss.org/browse/JBIDE-13232
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: Build/Releng
> Affects Versions: 4.1.0.Alpha1
> Environment:
> Reporter: Max Rydahl Andersen
> Assignee: Mickael Istria
> Fix For: 4.1.0.Alpha1
>
>
> .target files are all called "e42-wtp34-jbds6" even though they are for jbosstools and not specific to jbds6 either.
> Makes it hard to actually see which target platform to choose
--
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
13 years, 4 months
[JBoss JIRA] (JBIDE-13326) include Juno SR1+ performance fix in target platform? new connector on Central? In Installer?
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13326?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-13326:
----------------------------------------
About the performance feature, IMO, the best for users would be:
* This should be added to installer
* This should be part of our dependency site
* This should be part of Central as a "Highly Recommanded Fix"
But since 1 and 2 would require a respin, maybe we can just think that 3 is enough.
About the system properties in the .ini, I'm OK with what you suggested, but as far as I understand, this would only be available to users after a respin. We must keep in mind that if we go for setting these properties in JBT, we should ensure we don't set them in some other p2.inf for JBT and JBDS.
> include Juno SR1+ performance fix in target platform? new connector on Central? In Installer?
> ---------------------------------------------------------------------------------------------
>
> Key: JBIDE-13326
> URL: https://issues.jboss.org/browse/JBIDE-13326
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central, target-platform, updatesite
> Affects Versions: 4.0.0.Final
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Blocker
> Fix For: 4.0.1.Final
>
>
> Info: https://bugs.eclipse.org/bugs/show_bug.cgi?id=385272, http://wiki.eclipse.org/Platform_UI/Juno_Performance_Investigation
> Update Site: http://download.eclipse.org/eclipse/updates/4.2 --> Eclipse UI Juno SR1 Optimizations should be installed
> For Juno SR2 maintenance builds >= Nov 21, patch feature not needed.
> We could also consider setting these vmargs when installing JBT (community cental feature?) and/or JBDS BYOE:
> {code}
> -Xmn128m
> -Xms1024m
> -Xmx1024m
> -Xss2m
> -XX:PermSize=256m
> -XX:MaxPermSize=384m
> {code}
--
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
13 years, 4 months
[JBoss JIRA] (JBIDE-13232) refactor target platforms' GAVs, names, labels (was target platforms has the same name)
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13232?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-13232:
---------------------------------------------
about multiple git repos - ok, misunderstood that initial suggestion then.
About jbosstools-build only have 2 files in it ... not a big thing for me; the parent pom deserves strict versioning too.
About branching vs tagging I assume branching is needed for 1.430.x, 1.431.x etc. and tagging is not sufficient here.
> refactor target platforms' GAVs, names, labels (was target platforms has the same name)
> ---------------------------------------------------------------------------------------
>
> Key: JBIDE-13232
> URL: https://issues.jboss.org/browse/JBIDE-13232
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: Build/Releng
> Affects Versions: 4.1.0.Alpha1
> Environment:
> Reporter: Max Rydahl Andersen
> Assignee: Mickael Istria
> Fix For: 4.1.0.Alpha1
>
>
> .target files are all called "e42-wtp34-jbds6" even though they are for jbosstools and not specific to jbds6 either.
> Makes it hard to actually see which target platform to choose
--
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
13 years, 4 months
[JBoss JIRA] (JBIDE-13232) refactor target platforms' GAVs, names, labels (was target platforms has the same name)
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13232?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-13232 at 12/21/12 2:06 AM:
--------------------------------------------------------------
(Edited by Max to have the repo path only show the relevant parts)
Here's my proposal:
{quote}
* *Path:*
*JBT 4.0 (current):*
{code}
jbosstools-build/target-platforms/
jbdevstudio-{4.2.0.c,4.2.1.a}/
jbosstools-{4.2.0.c,4.2.1.a}/
pom.xml
multiple/pom.xml
multiple/multiple.target
unified/pom.xml
{code}
*JBT 4.1 (proposed):*
{code}
jbosstools-build/target-platforms/
{minimum,maximum}/
pom.xml
jbosstools-tp-with-sources/pom.xml
jbosstools-tp-with-sources/jbosstools-tp-with-sources.target
jbosstools-tp-no-sources/pom.xml
jbdevstudio-tp-with-sources/pom.xml
jbdevstudio-tp-with-sources/jbdevstudio-tp-with-sources.target
jbdevstudio-tp-no-sources/pom.xml
{code}
* *Pom version:*
*JBT 4.0 (current):*
{code}
root: 4.1.0.Alpha1-SNAPSHOT (used to be tied to parent pom version, then later just the same version)
minimums: 4.2.0-SNAPSHOT, 4.2.0.a-SNAPSHOT, 4.2.0.b-SNAPSHOT, 4.2.0.c-SNAPSHOT
maximums: 4.2.1.a-SNAPSHOT, 4.2.1-SNAPSHOT
{code}
*JBT 4.1 (proposed):*
{code}
root: 4.1.0-SNAPSHOT (not published, shouldn't have to increment it unless testing new version of Tycho or adding new profiles?)
minimum: 1.430.0, 1.430.1, ... (note that SNAPSHOT is dropped)
maximum (after July release): 1.431.0, 1.431.1, ... (note that SNAPSHOT is dropped)
{code}
* *Pom Params:*
*JBT 4.0 (current):*
{code}
<name>jbosstools Multiple (Composite) Target Platform 4.2.1.a</name>
<groupId>org.jboss.tools.target-platforms.jbosstools</groupId>
<artifactId>multiple</artifactId>
<version>4.2.1.a-SNAPSHOT</version>
<name>jbosstools Unified (Aggregate) Target Platform 4.2.1.a</name>
<groupId>org.jboss.tools.target-platforms.jbosstools</groupId>
<artifactId>unified</artifactId>
<version>4.2.1.a-SNAPSHOT</version>
{code}
*JBT 4.1 (proposed):*
{code}
<name>JBoss Tools Target Platform - Multiple URLs With Sources</name>
<groupId>org.jboss.tools.target-platforms</groupId> (drops the ".jbosstools" segment)
<artifactId>jbosstools-tp-with-sources</artifactId>
<version>1.430.0</version>
<name>JBoss Tools Target Platform - Unified URL Without Sources</name>
<groupId>org.jboss.tools.target-platforms</groupId> (drops the ".jbosstools" segment)
<artifactId>jbosstools-tp-no-sources</artifactId>
<version>1.430.0</version>
{code}
* *.target file name attribute:*
*JBT 4.0 (current):*
{code}
<target name="jbosstools-4.2.1.a">
<target name="jbdevstudio-4.2.1.a">
{code}
*JBT 4.1 (proposed):*
{code}
<target name="jbosstools-tp-with-sources-1.430.0">
<target name="jbdevstudio-tp-with-sources-1.430.0">
{code}
* *Maven/POM Path:*
*JBT 4.0 (current):*
{code}
<snapshot-repo>/org/jboss/tools/target-platforms/jbosstools/multiple/4.2.0.c-SNAPSHOT/
<snapshot-repo>/org/jboss/tools/target-platforms/jbosstools/unified/4.2.0.c-SNAPSHOT/
<snapshot-repo>/org/jboss/tools/target-platforms/jbosstools/multiple/4.2.1.a-SNAPSHOT/
<snapshot-repo>/org/jboss/tools/target-platforms/jbosstools/unified/4.2.1.a-SNAPSHOT/
{code}
*JBT 4.1 (proposed):*
{code}
<release-repo>/org/jboss/tools/target-platforms/jbosstools-tp-with-sources/1.430.0
<release-repo>/org/jboss/tools/target-platforms/jbosstools-tp-no-sources/1.430.0
<release-repo>/org/jboss/tools/target-platforms/jbosstools-tp-with-sources/1.431.0
<release-repo>/org/jboss/tools/target-platforms/jbosstools-tp-no-sources/1.431.0
{code}
{quote}
was (Author: nickboldt):
(Edited by Max to have the repo path only show the relevant parts)
Here's my proposal:
{quote}
* *Path:*
*JBT 4.0 (current):*
{code}
jbosstools-build/target-platforms/
jbdevstudio-{4.2.0.c,4.2.1.a}/
jbosstools-{4.2.0.c,4.2.1.a}/
pom.xml
multiple/pom.xml, multiple.target
unified/pom.xml
{code}
*JBT 4.1 (proposed):*
{code}
jbosstools-build/target-platforms/
{minimum,maximum}/
pom.xml
jbosstools-tp-with-sources/pom.xml, jbosstools-tp-with-sources.target
jbosstools-tp-no-sources/pom.xml
jbdevstudio-tp-with-sources/pom.xml, jbdevstudio-tp-with-sources.target
jbdevstudio-tp-no-sources/pom.xml
{code}
* *Pom version:*
*JBT 4.0 (current):*
{code}
root: 4.1.0.Alpha1-SNAPSHOT (used to be tied to parent pom version, then later just the same version)
minimums: 4.2.0-SNAPSHOT, 4.2.0.a-SNAPSHOT, 4.2.0.b-SNAPSHOT, 4.2.0.c-SNAPSHOT
maximums: 4.2.1.a-SNAPSHOT, 4.2.1-SNAPSHOT
{code}
*JBT 4.1 (proposed):*
{code}
root: 4.1.0-SNAPSHOT (not published, shouldn't have to increment it unless testing new version of Tycho or adding new profiles?)
minimum: 1.430.0, 1.430.1, ... (note that SNAPSHOT is dropped)
maximum (after July release): 1.431.0, 1.431.1, ... (note that SNAPSHOT is dropped)
{code}
* *Pom Params:*
*JBT 4.0 (current):*
{code}
<name>jbosstools Multiple (Composite) Target Platform 4.2.1.a</name>
<groupId>org.jboss.tools.target-platforms.jbosstools</groupId>
<artifactId>multiple</artifactId>
<version>4.2.1.a-SNAPSHOT</version>
<name>jbosstools Unified (Aggregate) Target Platform 4.2.1.a</name>
<groupId>org.jboss.tools.target-platforms.jbosstools</groupId>
<artifactId>unified</artifactId>
<version>4.2.1.a-SNAPSHOT</version>
{code}
*JBT 4.1 (proposed):*
{code}
<name>JBoss Tools Target Platform - Multiple URLs With Sources</name>
<groupId>org.jboss.tools.target-platforms</groupId> (drops the ".jbosstools" segment)
<artifactId>jbosstools-tp-with-sources</artifactId>
<version>1.430.0</version>
<name>JBoss Tools Target Platform - Unified URL Without Sources</name>
<groupId>org.jboss.tools.target-platforms</groupId> (drops the ".jbosstools" segment)
<artifactId>jbosstools-tp-no-sources</artifactId>
<version>1.430.0</version>
{code}
* *.target file name attribute:*
*JBT 4.0 (current):*
{code}
<target name="jbosstools-4.2.1.a">
<target name="jbdevstudio-4.2.1.a">
{code}
*JBT 4.1 (proposed):*
{code}
<target name="jbosstools-tp-with-sources-1.430.0">
<target name="jbdevstudio-tp-with-sources-1.430.0">
{code}
* *Maven/POM Path:*
*JBT 4.0 (current):*
{code}
<snapshot-repo>/org/jboss/tools/target-platforms/jbosstools/multiple/4.2.0.c-SNAPSHOT/
<snapshot-repo>/org/jboss/tools/target-platforms/jbosstools/unified/4.2.0.c-SNAPSHOT/
<snapshot-repo>/org/jboss/tools/target-platforms/jbosstools/multiple/4.2.1.a-SNAPSHOT/
<snapshot-repo>/org/jboss/tools/target-platforms/jbosstools/unified/4.2.1.a-SNAPSHOT/
{code}
*JBT 4.1 (proposed):*
{code}
<release-repo>/org/jboss/tools/target-platforms/jbosstools-tp-with-sources/1.430.0
<release-repo>/org/jboss/tools/target-platforms/jbosstools-tp-no-sources/1.430.0
<release-repo>/org/jboss/tools/target-platforms/jbosstools-tp-with-sources/1.431.0
<release-repo>/org/jboss/tools/target-platforms/jbosstools-tp-no-sources/1.431.0
{code}
{quote}
> refactor target platforms' GAVs, names, labels (was target platforms has the same name)
> ---------------------------------------------------------------------------------------
>
> Key: JBIDE-13232
> URL: https://issues.jboss.org/browse/JBIDE-13232
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: Build/Releng
> Affects Versions: 4.1.0.Alpha1
> Environment:
> Reporter: Max Rydahl Andersen
> Assignee: Mickael Istria
> Fix For: 4.1.0.Alpha1
>
>
> .target files are all called "e42-wtp34-jbds6" even though they are for jbosstools and not specific to jbds6 either.
> Makes it hard to actually see which target platform to choose
--
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
13 years, 4 months
[JBoss JIRA] (JBIDE-13232) refactor target platforms' GAVs, names, labels (was target platforms has the same name)
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13232?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen edited comment on JBIDE-13232 at 12/21/12 2:02 AM:
-----------------------------------------------------------------------
(Edited by Max to have the repo path only show the relevant parts)
Here's my proposal:
{quote}
* *Path:*
*JBT 4.0 (current):*
{code}
jbosstools-build/target-platforms/
jbdevstudio-{4.2.0.c,4.2.1.a}/
jbosstools-{4.2.0.c,4.2.1.a}/
pom.xml
multiple/pom.xml, multiple.target
unified/pom.xml
{code}
*JBT 4.1 (proposed):*
{code}
jbosstools-build/target-platforms/
{minimum,maximum}/
pom.xml
jbosstools-tp-with-sources/pom.xml, jbosstools-tp-with-sources.target
jbosstools-tp-no-sources/pom.xml
jbdevstudio-tp-with-sources/pom.xml, jbdevstudio-tp-with-sources.target
jbdevstudio-tp-no-sources/pom.xml
{code}
* *Pom version:*
*JBT 4.0 (current):*
{code}
root: 4.1.0.Alpha1-SNAPSHOT (used to be tied to parent pom version, then later just the same version)
minimums: 4.2.0-SNAPSHOT, 4.2.0.a-SNAPSHOT, 4.2.0.b-SNAPSHOT, 4.2.0.c-SNAPSHOT
maximums: 4.2.1.a-SNAPSHOT, 4.2.1-SNAPSHOT
{code}
*JBT 4.1 (proposed):*
{code}
root: 4.1.0-SNAPSHOT (not published, shouldn't have to increment it unless testing new version of Tycho or adding new profiles?)
minimum: 1.430.0, 1.430.1, ... (note that SNAPSHOT is dropped)
maximum (after July release): 1.431.0, 1.431.1, ... (note that SNAPSHOT is dropped)
{code}
* *Pom Params:*
*JBT 4.0 (current):*
{code}
<name>jbosstools Multiple (Composite) Target Platform 4.2.1.a</name>
<groupId>org.jboss.tools.target-platforms.jbosstools</groupId>
<artifactId>multiple</artifactId>
<version>4.2.1.a-SNAPSHOT</version>
<name>jbosstools Unified (Aggregate) Target Platform 4.2.1.a</name>
<groupId>org.jboss.tools.target-platforms.jbosstools</groupId>
<artifactId>unified</artifactId>
<version>4.2.1.a-SNAPSHOT</version>
{code}
*JBT 4.1 (proposed):*
{code}
<name>JBoss Tools Target Platform - Multiple URLs With Sources</name>
<groupId>org.jboss.tools.target-platforms</groupId> (drops the ".jbosstools" segment)
<artifactId>jbosstools-tp-with-sources</artifactId>
<version>1.430.0</version>
<name>JBoss Tools Target Platform - Unified URL Without Sources</name>
<groupId>org.jboss.tools.target-platforms</groupId> (drops the ".jbosstools" segment)
<artifactId>jbosstools-tp-no-sources</artifactId>
<version>1.430.0</version>
{code}
* *.target file name attribute:*
*JBT 4.0 (current):*
{code}
<target name="jbosstools-4.2.1.a">
<target name="jbdevstudio-4.2.1.a">
{code}
*JBT 4.1 (proposed):*
{code}
<target name="jbosstools-tp-with-sources-1.430.0">
<target name="jbdevstudio-tp-with-sources-1.430.0">
{code}
* *Maven/POM Path:*
*JBT 4.0 (current):*
{code}
<snapshot-repo>/org/jboss/tools/target-platforms/jbosstools/multiple/4.2.0.c-SNAPSHOT/
<snapshot-repo>/org/jboss/tools/target-platforms/jbosstools/unified/4.2.0.c-SNAPSHOT/
<snapshot-repo>/org/jboss/tools/target-platforms/jbosstools/multiple/4.2.1.a-SNAPSHOT/
<snapshot-repo>/org/jboss/tools/target-platforms/jbosstools/unified/4.2.1.a-SNAPSHOT/
{code}
*JBT 4.1 (proposed):*
{code}
<release-repo>/org/jboss/tools/target-platforms/jbosstools-tp-with-sources/1.430.0
<release-repo>/org/jboss/tools/target-platforms/jbosstools-tp-no-sources/1.430.0
<release-repo>/org/jboss/tools/target-platforms/jbosstools-tp-with-sources/1.431.0
<release-repo>/org/jboss/tools/target-platforms/jbosstools-tp-no-sources/1.431.0
{code}
{quote}
was (Author: nickboldt):
(Edited by Max to have the repo path only show the relevant parts)
Here's my proposal:
{quote}
* *Path:*
*JBT 4.0 (current):*
{code}
jbosstools-build/target-platforms/
jbdevstudio-{4.2.0.c,4.2.1.a}/
jbosstools-{4.2.0.c,4.2.1.a}/
pom.xml
multiple/pom.xml, multiple.target
unified/pom.xml
{code}
*JBT 4.1 (proposed):*
{code}
jbosstools-build/target-platforms/
{minimum,maximum}/
pom.xml
jbosstools-tp-with-sources/pom.xml, jbosstools-tp-with-sources.target
jbosstools-tp-no-sources/pom.xml
jbdevstudio-tp-with-sources/pom.xml, jbdevstudio-tp-with-sources.target
jbdevstudio-tp-no-sources/pom.xml
{code}
* *Pom version:*
*JBT 4.0 (current):*
{code}
root: 4.1.0.Alpha1-SNAPSHOT (used to be tied to parent pom version, then later just the same version)
minimums: 4.2.0-SNAPSHOT, 4.2.0.a-SNAPSHOT, 4.2.0.b-SNAPSHOT, 4.2.0.c-SNAPSHOT
maximums: 4.2.1.a-SNAPSHOT, 4.2.1-SNAPSHOT
{code}
*JBT 4.1 (proposed):*
{code}
root: 4.1.0-SNAPSHOT (not published, shouldn't have to increment it unless testing new version of Tycho or adding new profiles?)
minimum: 1.430.0, 1.430.1, ... (note that SNAPSHOT is dropped)
maximum (after July release): 1.431.0, 1.431.1, ... (note that SNAPSHOT is dropped)
{code}
* *Pom Params:*
*JBT 4.0 (current):*
{code}
<name>jbosstools Multiple (Composite) Target Platform 4.2.1.a</name>
<groupId>org.jboss.tools.target-platforms.jbosstools</groupId>
<artifactId>multiple</artifactId>
<version>4.2.1.a-SNAPSHOT</version>
<name>jbosstools Unified (Aggregate) Target Platform 4.2.1.a</name>
<groupId>org.jboss.tools.target-platforms.jbosstools</groupId>
<artifactId>unified</artifactId>
<version>4.2.1.a-SNAPSHOT</version>
{code}
*JBT 4.1 (proposed):*
{code}
<name>JBoss Tools Target Platform - Multiple URLs With Sources</name>
<groupId>org.jboss.tools.target-platforms</groupId> (drops the ".jbosstools" segment)
<artifactId>jbosstools-tp-with-sources</artifactId>
<version>1.430.0</version>
<name>JBoss Tools Target Platform - Unified URL Without Sources</name>
<groupId>org.jboss.tools.target-platforms</groupId> (drops the ".jbosstools" segment)
<artifactId>jbosstools-tp-no-sources</artifactId>
<version>1.430.0</version>
{code}
* *.target file name attribute:*
*JBT 4.0 (current):*
{code}
<target name="jbosstools-4.2.1.a">
<target name="jbdevstudio-4.2.1.a">
{code}
*JBT 4.1 (proposed):*
{code}
<target name="jbosstools-tp-with-sources-1.430.0">
<target name="jbdevstudio-tp-with-sources-1.430.0">
{code}
* *Maven/POM Path:*
*JBT 4.0 (current):*
{code}
<repo>/org/jboss/tools/target-platforms/jbosstools/multiple/4.2.0.c-SNAPSHOT/
<repo>/org/jboss/tools/target-platforms/jbosstools/unified/4.2.0.c-SNAPSHOT/
<repo>/org/jboss/tools/target-platforms/jbosstools/multiple/4.2.1.a-SNAPSHOT/
<repo>/org/jboss/tools/target-platforms/jbosstools/unified/4.2.1.a-SNAPSHOT/
{code}
*JBT 4.1 (proposed):*
{code}
<repo>/org/jboss/tools/target-platforms/jbosstools-tp-with-sources/1.430.0
<repo>/org/jboss/tools/target-platforms/jbosstools-tp-no-sources/1.430.0
<repo>/org/jboss/tools/target-platforms/jbosstools-tp-with-sources/1.431.0
<repo>/org/jboss/tools/target-platforms/jbosstools-tp-no-sources/1.431.0
{code}
{quote}
> refactor target platforms' GAVs, names, labels (was target platforms has the same name)
> ---------------------------------------------------------------------------------------
>
> Key: JBIDE-13232
> URL: https://issues.jboss.org/browse/JBIDE-13232
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: Build/Releng
> Affects Versions: 4.1.0.Alpha1
> Environment:
> Reporter: Max Rydahl Andersen
> Assignee: Mickael Istria
> Fix For: 4.1.0.Alpha1
>
>
> .target files are all called "e42-wtp34-jbds6" even though they are for jbosstools and not specific to jbds6 either.
> Makes it hard to actually see which target platform to choose
--
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
13 years, 4 months
[JBoss JIRA] (JBIDE-13232) refactor target platforms' GAVs, names, labels (was target platforms has the same name)
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13232?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-13232 at 12/21/12 2:01 AM:
--------------------------------------------------------------
Nick - in the new proposal wouldn't there be multiple git repositories instead of just putting it in jbosstools-build/target-platforms to allow proper tagging/versioning or how ?
something like:
{code}
jbosstools-tp/
pom.xml
no-sources/
pom.xml
jbosstools-tp-no-sources.target
with-sources/
pom.xml
jbosstools-tp-with-sources.target
devstudio-tp/
pom.xml
no-sources/
with-sources/
etc.
{code}
was (Author: maxandersen):
Nick - in the new proposal wouldn't there be multiple git repositories instead of just putting it in jbosstools-build/target-platforms to allow proper tagging/versioning or how ?
something like:
{code]
jbosstools-tp/
pom.xml
no-sources/
pom.xml
jbosstools-tp-no-sources.target
with-sources/
pom.xml
jbosstools-tp-with-sources.target
devstudio-tp/
pom.xml
no-sources/
with-sources/
etc.
{code}
> refactor target platforms' GAVs, names, labels (was target platforms has the same name)
> ---------------------------------------------------------------------------------------
>
> Key: JBIDE-13232
> URL: https://issues.jboss.org/browse/JBIDE-13232
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: Build/Releng
> Affects Versions: 4.1.0.Alpha1
> Environment:
> Reporter: Max Rydahl Andersen
> Assignee: Mickael Istria
> Fix For: 4.1.0.Alpha1
>
>
> .target files are all called "e42-wtp34-jbds6" even though they are for jbosstools and not specific to jbds6 either.
> Makes it hard to actually see which target platform to choose
--
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
13 years, 4 months
[JBoss JIRA] (JBIDE-13232) refactor target platforms' GAVs, names, labels (was target platforms has the same name)
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13232?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen edited comment on JBIDE-13232 at 12/21/12 2:01 AM:
-----------------------------------------------------------------------
Nick - in the new proposal wouldn't there be multiple git repositories instead of just putting it in jbosstools-build/target-platforms to allow proper tagging/versioning or how ?
something like:
{code}
jbosstools-tp/
pom.xml
no-sources/
pom.xml
jbosstools-tp-no-sources.target
with-sources/
pom.xml
jbosstools-tp-with-sources.target
devstudio-tp/
pom.xml
no-sources/
with-sources/
etc.
{code}
was (Author: maxandersen):
Nick - in the new proposal wouldn't there be multiple git repositories instead of just putting it in jbosstools-build/target-platforms to allow proper tagging/versioning or how ?
something like:
{code}
jbosstools-tp/
pom.xml
no-sources/
pom.xml
jbosstools-tp-no-sources.target
with-sources/
pom.xml
jbosstools-tp-with-sources.target
devstudio-tp/
pom.xml
no-sources/
with-sources/
etc.
{code}
> refactor target platforms' GAVs, names, labels (was target platforms has the same name)
> ---------------------------------------------------------------------------------------
>
> Key: JBIDE-13232
> URL: https://issues.jboss.org/browse/JBIDE-13232
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: Build/Releng
> Affects Versions: 4.1.0.Alpha1
> Environment:
> Reporter: Max Rydahl Andersen
> Assignee: Mickael Istria
> Fix For: 4.1.0.Alpha1
>
>
> .target files are all called "e42-wtp34-jbds6" even though they are for jbosstools and not specific to jbds6 either.
> Makes it hard to actually see which target platform to choose
--
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
13 years, 4 months
[JBoss JIRA] (JBIDE-13232) refactor target platforms' GAVs, names, labels (was target platforms has the same name)
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13232?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen edited comment on JBIDE-13232 at 12/21/12 1:59 AM:
-----------------------------------------------------------------------
Nick - in the new proposal wouldn't there be multiple git repositories instead of just putting it in jbosstools-build/target-platforms to allow proper tagging/versioning or how ?
something like:
{code]
jbosstools-tp/
pom.xml
no-sources/
pom.xml
jbosstools-tp-no-sources.target
with-sources/
pom.xml
jbosstools-tp-with-sources.target
devstudio-tp/
pom.xml
no-sources/
with-sources/
etc.
{code}
was (Author: maxandersen):
Nick - in the new proposal wouldn't there be multiple git repositories instead of just putting it in jbosstools-build/target-platforms to allow proper tagging/versioning or how ?
something like:
jbosstools-tp/
pom.xml
no-sources/
pom.xml
jbosstools-tp-no-sources.target
with-sources/
pom.xml
jbosstools-tp-with-sources.target
devstudio-tp/
pom.xml
no-sources/
with-sources/
etc.
> refactor target platforms' GAVs, names, labels (was target platforms has the same name)
> ---------------------------------------------------------------------------------------
>
> Key: JBIDE-13232
> URL: https://issues.jboss.org/browse/JBIDE-13232
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: Build/Releng
> Affects Versions: 4.1.0.Alpha1
> Environment:
> Reporter: Max Rydahl Andersen
> Assignee: Mickael Istria
> Fix For: 4.1.0.Alpha1
>
>
> .target files are all called "e42-wtp34-jbds6" even though they are for jbosstools and not specific to jbds6 either.
> Makes it hard to actually see which target platform to choose
--
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
13 years, 4 months
[JBoss JIRA] (JBIDE-13232) refactor target platforms' GAVs, names, labels (was target platforms has the same name)
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13232?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen edited comment on JBIDE-13232 at 12/21/12 1:55 AM:
-----------------------------------------------------------------------
Nick - in the new proposal wouldn't there be multiple git repositories instead of just putting it in jbosstools-build/target-platforms to allow proper tagging/versioning or how ?
something like:
jbosstools-tp/
pom.xml
no-sources/
pom.xml
jbosstools-tp-no-sources.target
with-sources/
pom.xml
jbosstools-tp-with-sources.target
devstudio-tp/
pom.xml
no-sources/
with-sources/
etc.
was (Author: maxandersen):
Nick - in the new proposal wouldn't there be multiple git repositories instead of just putting it in jbosstools-build/target-platforms to allow proper tagging/versioning or how ?
> refactor target platforms' GAVs, names, labels (was target platforms has the same name)
> ---------------------------------------------------------------------------------------
>
> Key: JBIDE-13232
> URL: https://issues.jboss.org/browse/JBIDE-13232
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: Build/Releng
> Affects Versions: 4.1.0.Alpha1
> Environment:
> Reporter: Max Rydahl Andersen
> Assignee: Mickael Istria
> Fix For: 4.1.0.Alpha1
>
>
> .target files are all called "e42-wtp34-jbds6" even though they are for jbosstools and not specific to jbds6 either.
> Makes it hard to actually see which target platform to choose
--
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
13 years, 4 months