[JBoss JIRA] (JBIDE-13058) decouple versioning of parent pom from that of target platforms because some TPs are used for multiple parent poms
10:28 a.m.
Nick Boldt created JBIDE-13058:
----------------------------------
Summary: decouple versioning of parent pom from that of target platforms
because some TPs are used for multiple parent poms
Key: JBIDE-13058
URL: https://issues.jboss.org/browse/JBIDE-13058
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng, target-platform
Affects Versions: 4.0.0.Beta2
Reporter: Nick Boldt
Assignee: Nick Boldt
Fix For: 4.0.0.CR1
Currently, we have parent pom versioned 4.0.0.Beta2-SNAPSHOT (Beta2x branch) or
4.0.0.CR1-SNAPSHOT (master). This is fine.
However, we also have the same versions set for the various target platforms. This is no
longer fine, because while the TP definition is the same between the stable_branch and
trunk jobs, the VERSION differs and that means we have to publish the job TWICE to get the
correct artifacts into Nexus.
Overkill solution is to have 2 jobs for every TP definition - one for stable branch
(versioned 4.0.0.Beta2-SNAPSHOT) and another for trunk (versioned 4.0.0.CR1-SNAPSHOT).
Have this as of yesterday.
BETTER solution is to have the TP definitions versioned to match their path/filename.
Thus:
* poms in build/target-platforms/jbdevstudio-JunoSR1a (regardless of master or Beta2x
branch) should be versioned 6.0.0.JunoSR1a
* poms in build/target-platforms/jbosstools-JunoSR0c (regardless of master or Beta2x
branch) should be versioned 4.0.0.JunoSR0c
--
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
11:48 a.m.
[
https://issues.jboss.org/browse/JBIDE-13058?page=com.atlassian.jira.plugi...
]
Nick Boldt closed JBIDE-13058.
------------------------------
Labels: respin-a (was: )
Fix Version/s: 4.0.0.Beta2
(was: 4.0.0.CR1)
Resolution: Done
Looks good. Closing for Beta2 respin-a.
decouple versioning of parent pom from that of target platforms
because some TPs are used for multiple parent poms
------------------------------------------------------------------------------------------------------------------
Key: JBIDE-13058
URL: https://issues.jboss.org/browse/JBIDE-13058
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng, target-platform
Affects Versions: 4.0.0.Beta2
Reporter: Nick Boldt
Assignee: Nick Boldt
Labels: respin-a
Fix For: 4.0.0.Beta2
Currently, we have parent pom versioned 4.0.0.Beta2-SNAPSHOT (Beta2x branch) or
4.0.0.CR1-SNAPSHOT (master). This is fine.
However, we also have the same versions set for the various target platforms. This is no
longer fine, because while the TP definition is the same between the stable_branch and
trunk jobs, the VERSION differs and that means we have to publish the job TWICE to get the
correct artifacts into Nexus.
Overkill solution is to have 2 jobs for every TP definition - one for stable branch
(versioned 4.0.0.Beta2-SNAPSHOT) and another for trunk (versioned 4.0.0.CR1-SNAPSHOT).
Have this as of yesterday.
BETTER solution is to have the TP definitions versioned to match their path/filename.
Thus:
* poms in build/target-platforms/jbdevstudio-JunoSR1a (regardless of master or Beta2x
branch) should be versioned 6.0.0.JunoSR1a
* poms in build/target-platforms/jbosstools-JunoSR0c (regardless of master or Beta2x
branch) should be versioned 4.0.0.JunoSR0c
--
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
1:11 a.m.
[
https://issues.jboss.org/browse/JBIDE-13058?page=com.atlassian.jira.plugi...
]
Mickael Istria reassigned JBIDE-13058:
--------------------------------------
Assignee: Nick Boldt (was: Mickael Istria)
What about simply removing the 4.0.0 or ANY reference to a JBT version in TP versions?
decouple versioning of parent pom from that of target platforms
because some TPs are used for multiple parent poms
------------------------------------------------------------------------------------------------------------------
Key: JBIDE-13058
URL: https://issues.jboss.org/browse/JBIDE-13058
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng, target-platform
Affects Versions: 4.0.0.Beta2
Reporter: Nick Boldt
Assignee: Nick Boldt
Labels: respin-a
Fix For: 4.0.0.Beta2
Currently, we have parent pom versioned 4.0.0.Beta2-SNAPSHOT (Beta2x branch) or
4.0.0.CR1-SNAPSHOT (master). This is fine.
However, we also have the same versions set for the various target platforms. This is no
longer fine, because while the TP definition is the same between the stable_branch and
trunk jobs, the VERSION differs and that means we have to publish the job TWICE to get the
correct artifacts into Nexus.
Overkill solution is to have 2 jobs for every TP definition - one for stable branch
(versioned 4.0.0.Beta2-SNAPSHOT) and another for trunk (versioned 4.0.0.CR1-SNAPSHOT).
Have this as of yesterday.
BETTER solution is to have the TP definitions versioned to match their path/filename.
Thus:
* poms in build/target-platforms/jbdevstudio-JunoSR1a (regardless of master or Beta2x
branch) should be versioned 6.0.0.JunoSR1a
* poms in build/target-platforms/jbosstools-JunoSR0c (regardless of master or Beta2x
branch) should be versioned 4.0.0.JunoSR0c
--
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:35 p.m.
[
https://issues.jboss.org/browse/JBIDE-13058?page=com.atlassian.jira.plugi...
]
Nick Boldt commented on JBIDE-13058:
------------------------------------
well, we need to set versions for jbosstools-JunoSR1a, jbosstools-JunoSR0c,
jbdevstudio-JunoSR1a, and jbdevstudio-JunoSR0c.
I would be happy if the version of the TP was just 1.0.0-SNAPSHOT, because then we'd
always use the latest version of the collection of deps that are the given TP. When we cut
a new target platform, it would be JunoSR0d v 1.0.0-SNAPSHOT or JunoSR1b v 1.0.0-SNAPSHOT,
regardless if it's the JBT or JBDS one. Simpler, no?
We shouldn't need to have a different version of the TP for trunk and stable_branch;
in fact that's entirely redundant.
So, instead of
{quote}
https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo...
https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo...
https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo...
https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo...
... and similar for /multiple/ ...
https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo...
https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo...
https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo...
https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo...
... and similar for /multiple/ ...
{quote}
Could we have:
{quote}
https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo...
https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo...
https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo...
https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo...
{quote}
Could we also skip deploying the /multiple/ ones? Who needs them, when they have the
unified ones?
decouple versioning of parent pom from that of target platforms
because some TPs are used for multiple parent poms
------------------------------------------------------------------------------------------------------------------
Key: JBIDE-13058
URL: https://issues.jboss.org/browse/JBIDE-13058
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng, target-platform
Affects Versions: 4.0.0.Beta2
Reporter: Nick Boldt
Assignee: Nick Boldt
Labels: respin-a
Fix For: 4.0.0.Beta2
Currently, we have parent pom versioned 4.0.0.Beta2-SNAPSHOT (Beta2x branch) or
4.0.0.CR1-SNAPSHOT (master). This is fine.
However, we also have the same versions set for the various target platforms. This is no
longer fine, because while the TP definition is the same between the stable_branch and
trunk jobs, the VERSION differs and that means we have to publish the job TWICE to get the
correct artifacts into Nexus.
Overkill solution is to have 2 jobs for every TP definition - one for stable branch
(versioned 4.0.0.Beta2-SNAPSHOT) and another for trunk (versioned 4.0.0.CR1-SNAPSHOT).
Have this as of yesterday.
BETTER solution is to have the TP definitions versioned to match their path/filename.
Thus:
* poms in build/target-platforms/jbdevstudio-JunoSR1a (regardless of master or Beta2x
branch) should be versioned 6.0.0.JunoSR1a
* poms in build/target-platforms/jbosstools-JunoSR0c (regardless of master or Beta2x
branch) should be versioned 4.0.0.JunoSR0c
--
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:35 p.m.
[
https://issues.jboss.org/browse/JBIDE-13058?page=com.atlassian.jira.plugi...
]
Nick Boldt edited comment on JBIDE-13058 at 11/19/12 1:35 PM:
--------------------------------------------------------------
well, we need to set versions for jbosstools-JunoSR1a, jbosstools-JunoSR0c,
jbdevstudio-JunoSR1a, and jbdevstudio-JunoSR0c.
I would be happy if the version of the TP was just 1.0.0-SNAPSHOT, because then we'd
always use the latest version of the collection of deps that are the given TP. When we cut
a new target platform, it would be JunoSR0d v 1.0.0-SNAPSHOT or JunoSR1b v 1.0.0-SNAPSHOT,
regardless if it's the JBT or JBDS one. The TP version would ALWAYS be 1.0.0-SNAPSHOT
because if the contents change, we cut a new name (SR0x, SR1x, SR2x).
We shouldn't need to have a different version of the TP for trunk and stable_branch;
in fact that's entirely redundant.
So, instead of
{quote}
https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo...
https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo...
https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo...
https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo...
... and similar for /multiple/ ...
https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo...
https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo...
https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo...
https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo...
... and similar for /multiple/ ...
{quote}
Could we have:
{quote}
https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo...
https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo...
https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo...
https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo...
{quote}
Could we also skip deploying the /multiple/ ones? Who needs them, when they have the
unified ones?
was (Author: nickboldt):
well, we need to set versions for jbosstools-JunoSR1a, jbosstools-JunoSR0c,
jbdevstudio-JunoSR1a, and jbdevstudio-JunoSR0c.
I would be happy if the version of the TP was just 1.0.0-SNAPSHOT, because then we'd
always use the latest version of the collection of deps that are the given TP. When we cut
a new target platform, it would be JunoSR0d v 1.0.0-SNAPSHOT or JunoSR1b v 1.0.0-SNAPSHOT,
regardless if it's the JBT or JBDS one. Simpler, no?
We shouldn't need to have a different version of the TP for trunk and stable_branch;
in fact that's entirely redundant.
So, instead of
{quote}
https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo...
https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo...
https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo...
https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo...
... and similar for /multiple/ ...
https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo...
https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo...
https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo...
https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo...
... and similar for /multiple/ ...
{quote}
Could we have:
{quote}
https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo...
https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo...
https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo...
https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo...
{quote}
Could we also skip deploying the /multiple/ ones? Who needs them, when they have the
unified ones?
decouple versioning of parent pom from that of target platforms
because some TPs are used for multiple parent poms
------------------------------------------------------------------------------------------------------------------
Key: JBIDE-13058
URL: https://issues.jboss.org/browse/JBIDE-13058
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng, target-platform
Affects Versions: 4.0.0.Beta2
Reporter: Nick Boldt
Assignee: Nick Boldt
Labels: respin-a
Fix For: 4.0.0.Beta2
Currently, we have parent pom versioned 4.0.0.Beta2-SNAPSHOT (Beta2x branch) or
4.0.0.CR1-SNAPSHOT (master). This is fine.
However, we also have the same versions set for the various target platforms. This is no
longer fine, because while the TP definition is the same between the stable_branch and
trunk jobs, the VERSION differs and that means we have to publish the job TWICE to get the
correct artifacts into Nexus.
Overkill solution is to have 2 jobs for every TP definition - one for stable branch
(versioned 4.0.0.Beta2-SNAPSHOT) and another for trunk (versioned 4.0.0.CR1-SNAPSHOT).
Have this as of yesterday.
BETTER solution is to have the TP definitions versioned to match their path/filename.
Thus:
* poms in build/target-platforms/jbdevstudio-JunoSR1a (regardless of master or Beta2x
branch) should be versioned 6.0.0.JunoSR1a
* poms in build/target-platforms/jbosstools-JunoSR0c (regardless of master or Beta2x
branch) should be versioned 4.0.0.JunoSR0c
--
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:35 p.m.
[
https://issues.jboss.org/browse/JBIDE-13058?page=com.atlassian.jira.plugi...
]
Nick Boldt edited comment on JBIDE-13058 at 11/19/12 1:34 PM:
--------------------------------------------------------------
well, we need to set versions for jbosstools-JunoSR1a, jbosstools-JunoSR0c,
jbdevstudio-JunoSR1a, and jbdevstudio-JunoSR0c.
I would be happy if the version of the TP was just 1.0.0-SNAPSHOT, because then we'd
always use the latest version of the collection of deps that are the given TP. When we cut
a new target platform, it would be JunoSR0d v 1.0.0-SNAPSHOT or JunoSR1b v 1.0.0-SNAPSHOT,
regardless if it's the JBT or JBDS one. Simpler, no?
We shouldn't need to have a different version of the TP for trunk and stable_branch;
in fact that's entirely redundant.
So, instead of
{quote}
https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo...
https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo...
https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo...
https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo...
... and similar for /multiple/ ...
https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo...
https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo...
https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo...
https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo...
... and similar for /multiple/ ...
{quote}
Could we have:
{quote}
https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo...
https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo...
https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo...
https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo...
{quote}
Could we also skip deploying the /multiple/ ones? Who needs them, when they have the
unified ones?
was (Author: nickboldt):
well, we need to set versions for jbosstools-JunoSR1a, jbosstools-JunoSR0c,
jbdevstudio-JunoSR1a, and jbdevstudio-JunoSR0c.
I would be happy if the version of the TP was just 1.0.0-SNAPSHOT, because then we'd
always use the latest version of the collection of deps that are the given TP. When we cut
a new target platform, it would be JunoSR0d v 1.0.0-SNAPSHOT or JunoSR1b v 1.0.0-SNAPSHOT,
regardless if it's the JBT or JBDS one. Simpler, no?
We shouldn't need to have a different version of the TP for trunk and stable_branch;
in fact that's entirely redundant.
So, instead of
{quote}
https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo...
https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo...
https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo...
https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo...
... and similar for /multiple/ ...
https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo...
https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo...
https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo...
https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo...
... and similar for /multiple/ ...
{quote}
Could we have:
{quote}
https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo...
https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo...
https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo...
https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo...
{quote}
Could we also skip deploying the /multiple/ ones? Who needs them, when they have the
unified ones?
decouple versioning of parent pom from that of target platforms
because some TPs are used for multiple parent poms
------------------------------------------------------------------------------------------------------------------
Key: JBIDE-13058
URL: https://issues.jboss.org/browse/JBIDE-13058
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng, target-platform
Affects Versions: 4.0.0.Beta2
Reporter: Nick Boldt
Assignee: Nick Boldt
Labels: respin-a
Fix For: 4.0.0.Beta2
Currently, we have parent pom versioned 4.0.0.Beta2-SNAPSHOT (Beta2x branch) or
4.0.0.CR1-SNAPSHOT (master). This is fine.
However, we also have the same versions set for the various target platforms. This is no
longer fine, because while the TP definition is the same between the stable_branch and
trunk jobs, the VERSION differs and that means we have to publish the job TWICE to get the
correct artifacts into Nexus.
Overkill solution is to have 2 jobs for every TP definition - one for stable branch
(versioned 4.0.0.Beta2-SNAPSHOT) and another for trunk (versioned 4.0.0.CR1-SNAPSHOT).
Have this as of yesterday.
BETTER solution is to have the TP definitions versioned to match their path/filename.
Thus:
* poms in build/target-platforms/jbdevstudio-JunoSR1a (regardless of master or Beta2x
branch) should be versioned 6.0.0.JunoSR1a
* poms in build/target-platforms/jbosstools-JunoSR0c (regardless of master or Beta2x
branch) should be versioned 4.0.0.JunoSR0c
--
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:37 p.m.
[
https://issues.jboss.org/browse/JBIDE-13058?page=com.atlassian.jira.plugi...
]
Nick Boldt reassigned JBIDE-13058:
----------------------------------
Assignee: Mickael Istria (was: Nick Boldt)
decouple versioning of parent pom from that of target platforms
because some TPs are used for multiple parent poms
------------------------------------------------------------------------------------------------------------------
Key: JBIDE-13058
URL: https://issues.jboss.org/browse/JBIDE-13058
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng, target-platform
Affects Versions: 4.0.0.Beta2
Reporter: Nick Boldt
Assignee: Mickael Istria
Labels: respin-a
Fix For: 4.0.0.Beta2
Currently, we have parent pom versioned 4.0.0.Beta2-SNAPSHOT (Beta2x branch) or
4.0.0.CR1-SNAPSHOT (master). This is fine.
However, we also have the same versions set for the various target platforms. This is no
longer fine, because while the TP definition is the same between the stable_branch and
trunk jobs, the VERSION differs and that means we have to publish the job TWICE to get the
correct artifacts into Nexus.
Overkill solution is to have 2 jobs for every TP definition - one for stable branch
(versioned 4.0.0.Beta2-SNAPSHOT) and another for trunk (versioned 4.0.0.CR1-SNAPSHOT).
Have this as of yesterday.
BETTER solution is to have the TP definitions versioned to match their path/filename.
Thus:
* poms in build/target-platforms/jbdevstudio-JunoSR1a (regardless of master or Beta2x
branch) should be versioned 6.0.0.JunoSR1a
* poms in build/target-platforms/jbosstools-JunoSR0c (regardless of master or Beta2x
branch) should be versioned 4.0.0.JunoSR0c
--
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
1:42 a.m.
[
https://issues.jboss.org/browse/JBIDE-13058?page=com.atlassian.jira.plugi...
]
Mickael Istria commented on JBIDE-13058:
----------------------------------------
And what about following Eclipse versioning?
So we remove junoSRx from GroupId and ArtifactId and we use 4.2.1, 4.2.1.a and so on.
Se we'd see:
* org/jbosstools/target-platforms/multiple/4.2.0.c-SNAPSHOT
* org/jbosstools/target-platforms/unified/4.2.0.c-SNAPSHOT
* org/jbosstools/target-platforms/multiple/4.2.1.a-SNAPSHOT
* org/jbosstools/target-platforms/unified/4.2.1.a-SNAPSHOT
...
JBDS could have a different groupId
* com/jbds/target-platforms/multiple/4.2.0.c-SNAPSHOT
* ...
decouple versioning of parent pom from that of target platforms
because some TPs are used for multiple parent poms
------------------------------------------------------------------------------------------------------------------
Key: JBIDE-13058
URL: https://issues.jboss.org/browse/JBIDE-13058
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng, target-platform
Affects Versions: 4.0.0.Beta2
Reporter: Nick Boldt
Assignee: Mickael Istria
Labels: respin-a
Fix For: 4.0.0.Beta2
Currently, we have parent pom versioned 4.0.0.Beta2-SNAPSHOT (Beta2x branch) or
4.0.0.CR1-SNAPSHOT (master). This is fine.
However, we also have the same versions set for the various target platforms. This is no
longer fine, because while the TP definition is the same between the stable_branch and
trunk jobs, the VERSION differs and that means we have to publish the job TWICE to get the
correct artifacts into Nexus.
Overkill solution is to have 2 jobs for every TP definition - one for stable branch
(versioned 4.0.0.Beta2-SNAPSHOT) and another for trunk (versioned 4.0.0.CR1-SNAPSHOT).
Have this as of yesterday.
BETTER solution is to have the TP definitions versioned to match their path/filename.
Thus:
* poms in build/target-platforms/jbdevstudio-JunoSR1a (regardless of master or Beta2x
branch) should be versioned 6.0.0.JunoSR1a
* poms in build/target-platforms/jbosstools-JunoSR0c (regardless of master or Beta2x
branch) should be versioned 4.0.0.JunoSR0c
--
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
4:21 a.m.
[
https://issues.jboss.org/browse/JBIDE-13058?page=com.atlassian.jira.plugi...
]
Mickael Istria commented on JBIDE-13058:
----------------------------------------
Also, TARGET_PLATFORM_VERSION in parent pom should not contain any reference to
${project.version} or ${JBT_VERSION}
decouple versioning of parent pom from that of target platforms
because some TPs are used for multiple parent poms
------------------------------------------------------------------------------------------------------------------
Key: JBIDE-13058
URL: https://issues.jboss.org/browse/JBIDE-13058
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng, target-platform
Affects Versions: 4.0.0.Beta2
Reporter: Nick Boldt
Assignee: Mickael Istria
Labels: respin-a
Fix For: 4.0.0.Beta2
Currently, we have parent pom versioned 4.0.0.Beta2-SNAPSHOT (Beta2x branch) or
4.0.0.CR1-SNAPSHOT (master). This is fine.
However, we also have the same versions set for the various target platforms. This is no
longer fine, because while the TP definition is the same between the stable_branch and
trunk jobs, the VERSION differs and that means we have to publish the job TWICE to get the
correct artifacts into Nexus.
Overkill solution is to have 2 jobs for every TP definition - one for stable branch
(versioned 4.0.0.Beta2-SNAPSHOT) and another for trunk (versioned 4.0.0.CR1-SNAPSHOT).
Have this as of yesterday.
BETTER solution is to have the TP definitions versioned to match their path/filename.
Thus:
* poms in build/target-platforms/jbdevstudio-JunoSR1a (regardless of master or Beta2x
branch) should be versioned 6.0.0.JunoSR1a
* poms in build/target-platforms/jbosstools-JunoSR0c (regardless of master or Beta2x
branch) should be versioned 4.0.0.JunoSR0c
--
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
8:43 a.m.
[
https://issues.jboss.org/browse/JBIDE-13058?page=com.atlassian.jira.plugi...
]
Mickael Istria commented on JBIDE-13058:
----------------------------------------
[~nickboldt] On this branch, I suggest TP version don't reference any JBT version (not
even the major). https://github.com/mickaelistria/jbosstools-build/tree/JBIDE-13058
decouple versioning of parent pom from that of target platforms
because some TPs are used for multiple parent poms
------------------------------------------------------------------------------------------------------------------
Key: JBIDE-13058
URL: https://issues.jboss.org/browse/JBIDE-13058
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng, target-platform
Affects Versions: 4.0.0.Beta2
Reporter: Nick Boldt
Assignee: Mickael Istria
Labels: respin-a
Fix For: 4.0.0.Beta2
Currently, we have parent pom versioned 4.0.0.Beta2-SNAPSHOT (Beta2x branch) or
4.0.0.CR1-SNAPSHOT (master). This is fine.
However, we also have the same versions set for the various target platforms. This is no
longer fine, because while the TP definition is the same between the stable_branch and
trunk jobs, the VERSION differs and that means we have to publish the job TWICE to get the
correct artifacts into Nexus.
Overkill solution is to have 2 jobs for every TP definition - one for stable branch
(versioned 4.0.0.Beta2-SNAPSHOT) and another for trunk (versioned 4.0.0.CR1-SNAPSHOT).
Have this as of yesterday.
BETTER solution is to have the TP definitions versioned to match their path/filename.
Thus:
* poms in build/target-platforms/jbdevstudio-JunoSR1a (regardless of master or Beta2x
branch) should be versioned 6.0.0.JunoSR1a
* poms in build/target-platforms/jbosstools-JunoSR0c (regardless of master or Beta2x
branch) should be versioned 4.0.0.JunoSR0c
--
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
11:56 a.m.
[
https://issues.jboss.org/browse/JBIDE-13058?page=com.atlassian.jira.plugi...
]
Nick Boldt updated JBIDE-13058:
-------------------------------
Fix Version/s: 4.0.0.CR2
(was: 4.0.0.Beta2)
decouple versioning of parent pom from that of target platforms
because some TPs are used for multiple parent poms
------------------------------------------------------------------------------------------------------------------
Key: JBIDE-13058
URL: https://issues.jboss.org/browse/JBIDE-13058
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng, target-platform
Affects Versions: 4.0.0.Beta2
Reporter: Nick Boldt
Assignee: Mickael Istria
Labels: respin-a
Fix For: 4.0.0.CR2
Currently, we have parent pom versioned 4.0.0.Beta2-SNAPSHOT (Beta2x branch) or
4.0.0.CR1-SNAPSHOT (master). This is fine.
However, we also have the same versions set for the various target platforms. This is no
longer fine, because while the TP definition is the same between the stable_branch and
trunk jobs, the VERSION differs and that means we have to publish the job TWICE to get the
correct artifacts into Nexus.
Overkill solution is to have 2 jobs for every TP definition - one for stable branch
(versioned 4.0.0.Beta2-SNAPSHOT) and another for trunk (versioned 4.0.0.CR1-SNAPSHOT).
Have this as of yesterday.
BETTER solution is to have the TP definitions versioned to match their path/filename.
Thus:
* poms in build/target-platforms/jbdevstudio-JunoSR1a (regardless of master or Beta2x
branch) should be versioned 6.0.0.JunoSR1a
* poms in build/target-platforms/jbosstools-JunoSR0c (regardless of master or Beta2x
branch) should be versioned 4.0.0.JunoSR0c
--
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
11:56 a.m.
[
https://issues.jboss.org/browse/JBIDE-13058?page=com.atlassian.jira.plugi...
]
Nick Boldt commented on JBIDE-13058:
------------------------------------
Do we even need to publish multiple, when unified includes the same content in a single
URL, avoiding extraneous IUs and extra p2 metadata loading, plus references to additional
sites?
Can we instead `mvn install` multiple, then `mvn install deploy` unified?
And if there's only 1 .target to publish, can we therefore drop the classifier and get
even simpler?
* org/jbosstools/target-platforms/4.2.0.c-SNAPSHOT
* org/jbosstools/target-platforms/4.2.1.a-SNAPSHOT
* com/jbds/target-platforms/4.2.0.c-SNAPSHOT
* com/jbds/target-platforms/4.2.1.a-SNAPSHOT
decouple versioning of parent pom from that of target platforms
because some TPs are used for multiple parent poms
------------------------------------------------------------------------------------------------------------------
Key: JBIDE-13058
URL: https://issues.jboss.org/browse/JBIDE-13058
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng, target-platform
Affects Versions: 4.0.0.Beta2
Reporter: Nick Boldt
Assignee: Mickael Istria
Labels: respin-a
Fix For: 4.0.0.CR2
Currently, we have parent pom versioned 4.0.0.Beta2-SNAPSHOT (Beta2x branch) or
4.0.0.CR1-SNAPSHOT (master). This is fine.
However, we also have the same versions set for the various target platforms. This is no
longer fine, because while the TP definition is the same between the stable_branch and
trunk jobs, the VERSION differs and that means we have to publish the job TWICE to get the
correct artifacts into Nexus.
Overkill solution is to have 2 jobs for every TP definition - one for stable branch
(versioned 4.0.0.Beta2-SNAPSHOT) and another for trunk (versioned 4.0.0.CR1-SNAPSHOT).
Have this as of yesterday.
BETTER solution is to have the TP definitions versioned to match their path/filename.
Thus:
* poms in build/target-platforms/jbdevstudio-JunoSR1a (regardless of master or Beta2x
branch) should be versioned 6.0.0.JunoSR1a
* poms in build/target-platforms/jbosstools-JunoSR0c (regardless of master or Beta2x
branch) should be versioned 4.0.0.JunoSR0c
--
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
11:56 a.m.
[
https://issues.jboss.org/browse/JBIDE-13058?page=com.atlassian.jira.plugi...
]
Nick Boldt commented on JBIDE-13058:
------------------------------------
Push out to CR2. Or maybe we want to only worry about this for the first Kepler-based
builds (4.3.0.a-SNAPSHOT) in Dec/Jan?
decouple versioning of parent pom from that of target platforms
because some TPs are used for multiple parent poms
------------------------------------------------------------------------------------------------------------------
Key: JBIDE-13058
URL: https://issues.jboss.org/browse/JBIDE-13058
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng, target-platform
Affects Versions: 4.0.0.Beta2
Reporter: Nick Boldt
Assignee: Mickael Istria
Labels: respin-a
Fix For: 4.0.0.CR2
Currently, we have parent pom versioned 4.0.0.Beta2-SNAPSHOT (Beta2x branch) or
4.0.0.CR1-SNAPSHOT (master). This is fine.
However, we also have the same versions set for the various target platforms. This is no
longer fine, because while the TP definition is the same between the stable_branch and
trunk jobs, the VERSION differs and that means we have to publish the job TWICE to get the
correct artifacts into Nexus.
Overkill solution is to have 2 jobs for every TP definition - one for stable branch
(versioned 4.0.0.Beta2-SNAPSHOT) and another for trunk (versioned 4.0.0.CR1-SNAPSHOT).
Have this as of yesterday.
BETTER solution is to have the TP definitions versioned to match their path/filename.
Thus:
* poms in build/target-platforms/jbdevstudio-JunoSR1a (regardless of master or Beta2x
branch) should be versioned 6.0.0.JunoSR1a
* poms in build/target-platforms/jbosstools-JunoSR0c (regardless of master or Beta2x
branch) should be versioned 4.0.0.JunoSR0c
--
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:06 p.m.
[
https://issues.jboss.org/browse/JBIDE-13058?page=com.atlassian.jira.plugi...
]
Mickael Istria commented on JBIDE-13058:
----------------------------------------
We should keep multiple since it's recommended to use it in IDE (it includes sources).
We should keep it deployed in case one day we ave troubles to build unified, or if we want
to build stuff from past and discover the aggregated sites disappeared. It's a nice
backup.
If we can make it for CR2, the sooner the better.
decouple versioning of parent pom from that of target platforms
because some TPs are used for multiple parent poms
------------------------------------------------------------------------------------------------------------------
Key: JBIDE-13058
URL: https://issues.jboss.org/browse/JBIDE-13058
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng, target-platform
Affects Versions: 4.0.0.Beta2
Reporter: Nick Boldt
Assignee: Mickael Istria
Labels: respin-a
Fix For: 4.0.0.CR2
Currently, we have parent pom versioned 4.0.0.Beta2-SNAPSHOT (Beta2x branch) or
4.0.0.CR1-SNAPSHOT (master). This is fine.
However, we also have the same versions set for the various target platforms. This is no
longer fine, because while the TP definition is the same between the stable_branch and
trunk jobs, the VERSION differs and that means we have to publish the job TWICE to get the
correct artifacts into Nexus.
Overkill solution is to have 2 jobs for every TP definition - one for stable branch
(versioned 4.0.0.Beta2-SNAPSHOT) and another for trunk (versioned 4.0.0.CR1-SNAPSHOT).
Have this as of yesterday.
BETTER solution is to have the TP definitions versioned to match their path/filename.
Thus:
* poms in build/target-platforms/jbdevstudio-JunoSR1a (regardless of master or Beta2x
branch) should be versioned 6.0.0.JunoSR1a
* poms in build/target-platforms/jbosstools-JunoSR0c (regardless of master or Beta2x
branch) should be versioned 4.0.0.JunoSR0c
--
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:23 p.m.
[
https://issues.jboss.org/browse/JBIDE-13058?page=com.atlassian.jira.plugi...
]
Rob Cernich commented on JBIDE-13058:
-------------------------------------
Is there a reason they need to be versioned SNAPSHOT? I like the idea of being able to
simply use the JBT blessed Juno TP by simply grabbing
org.jboss.tools.target-platforms:unified:4.2.1.a. Of course, I'm assuming the TP is
versioned independently from JBT.
decouple versioning of parent pom from that of target platforms
because some TPs are used for multiple parent poms
------------------------------------------------------------------------------------------------------------------
Key: JBIDE-13058
URL: https://issues.jboss.org/browse/JBIDE-13058
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng, target-platform
Affects Versions: 4.0.0.Beta2
Reporter: Nick Boldt
Assignee: Mickael Istria
Labels: respin-a
Fix For: 4.0.0.CR2
Currently, we have parent pom versioned 4.0.0.Beta2-SNAPSHOT (Beta2x branch) or
4.0.0.CR1-SNAPSHOT (master). This is fine.
However, we also have the same versions set for the various target platforms. This is no
longer fine, because while the TP definition is the same between the stable_branch and
trunk jobs, the VERSION differs and that means we have to publish the job TWICE to get the
correct artifacts into Nexus.
Overkill solution is to have 2 jobs for every TP definition - one for stable branch
(versioned 4.0.0.Beta2-SNAPSHOT) and another for trunk (versioned 4.0.0.CR1-SNAPSHOT).
Have this as of yesterday.
BETTER solution is to have the TP definitions versioned to match their path/filename.
Thus:
* poms in build/target-platforms/jbdevstudio-JunoSR1a (regardless of master or Beta2x
branch) should be versioned 6.0.0.JunoSR1a
* poms in build/target-platforms/jbosstools-JunoSR0c (regardless of master or Beta2x
branch) should be versioned 4.0.0.JunoSR0c
--
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
2:33 a.m.
[
https://issues.jboss.org/browse/JBIDE-13058?page=com.atlassian.jira.plugi...
]
Mickael Istria commented on JBIDE-13058:
----------------------------------------
The reason why we have SNAPSHOTs is the we sometimes build the TP several times (when we
see bugs), and we did not set up the process to turn the best TP into a release (without
-SNAPSHOT). That's something we'll for sure improve in the future, but for the
moment, we did not feel this as a priority.
The latest -SNAPSHOT is a stable target...
decouple versioning of parent pom from that of target platforms
because some TPs are used for multiple parent poms
------------------------------------------------------------------------------------------------------------------
Key: JBIDE-13058
URL: https://issues.jboss.org/browse/JBIDE-13058
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng, target-platform
Affects Versions: 4.0.0.Beta2
Reporter: Nick Boldt
Assignee: Mickael Istria
Labels: respin-a
Fix For: 4.0.0.CR2
Currently, we have parent pom versioned 4.0.0.Beta2-SNAPSHOT (Beta2x branch) or
4.0.0.CR1-SNAPSHOT (master). This is fine.
However, we also have the same versions set for the various target platforms. This is no
longer fine, because while the TP definition is the same between the stable_branch and
trunk jobs, the VERSION differs and that means we have to publish the job TWICE to get the
correct artifacts into Nexus.
Overkill solution is to have 2 jobs for every TP definition - one for stable branch
(versioned 4.0.0.Beta2-SNAPSHOT) and another for trunk (versioned 4.0.0.CR1-SNAPSHOT).
Have this as of yesterday.
BETTER solution is to have the TP definitions versioned to match their path/filename.
Thus:
* poms in build/target-platforms/jbdevstudio-JunoSR1a (regardless of master or Beta2x
branch) should be versioned 6.0.0.JunoSR1a
* poms in build/target-platforms/jbosstools-JunoSR0c (regardless of master or Beta2x
branch) should be versioned 4.0.0.JunoSR0c
--
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
3:37 a.m.
[
https://issues.jboss.org/browse/JBIDE-13058?page=com.atlassian.jira.plugi...
]
Mickael Istria updated JBIDE-13058:
-----------------------------------
Fix Version/s: 4.1.0.Alpha1
Since my JBIDE-13058 branch was forked from master after 4.0.x branch was forked, I think
it'll way easier to change it as part of the 4.1 stream.
Also, it's just an enhancement, so let's postpone it (just) after GA.
decouple versioning of parent pom from that of target platforms
because some TPs are used for multiple parent poms
------------------------------------------------------------------------------------------------------------------
Key: JBIDE-13058
URL: https://issues.jboss.org/browse/JBIDE-13058
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng, target-platform
Affects Versions: 4.0.0.Beta2
Reporter: Nick Boldt
Assignee: Mickael Istria
Labels: respin-a
Fix For: 4.0.0.CR2, 4.1.0.Alpha1
Currently, we have parent pom versioned 4.0.0.Beta2-SNAPSHOT (Beta2x branch) or
4.0.0.CR1-SNAPSHOT (master). This is fine.
However, we also have the same versions set for the various target platforms. This is no
longer fine, because while the TP definition is the same between the stable_branch and
trunk jobs, the VERSION differs and that means we have to publish the job TWICE to get the
correct artifacts into Nexus.
Overkill solution is to have 2 jobs for every TP definition - one for stable branch
(versioned 4.0.0.Beta2-SNAPSHOT) and another for trunk (versioned 4.0.0.CR1-SNAPSHOT).
Have this as of yesterday.
BETTER solution is to have the TP definitions versioned to match their path/filename.
Thus:
* poms in build/target-platforms/jbdevstudio-JunoSR1a (regardless of master or Beta2x
branch) should be versioned 6.0.0.JunoSR1a
* poms in build/target-platforms/jbosstools-JunoSR0c (regardless of master or Beta2x
branch) should be versioned 4.0.0.JunoSR0c
--
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
3:39 a.m.
[
https://issues.jboss.org/browse/JBIDE-13058?page=com.atlassian.jira.plugi...
]
Mickael Istria updated JBIDE-13058:
-----------------------------------
Fix Version/s: (was: 4.0.0.CR2)
decouple versioning of parent pom from that of target platforms
because some TPs are used for multiple parent poms
------------------------------------------------------------------------------------------------------------------
Key: JBIDE-13058
URL: https://issues.jboss.org/browse/JBIDE-13058
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng, target-platform
Affects Versions: 4.0.0.Beta2
Reporter: Nick Boldt
Assignee: Mickael Istria
Labels: respin-a
Fix For: 4.1.0.Alpha1
Currently, we have parent pom versioned 4.0.0.Beta2-SNAPSHOT (Beta2x branch) or
4.0.0.CR1-SNAPSHOT (master). This is fine.
However, we also have the same versions set for the various target platforms. This is no
longer fine, because while the TP definition is the same between the stable_branch and
trunk jobs, the VERSION differs and that means we have to publish the job TWICE to get the
correct artifacts into Nexus.
Overkill solution is to have 2 jobs for every TP definition - one for stable branch
(versioned 4.0.0.Beta2-SNAPSHOT) and another for trunk (versioned 4.0.0.CR1-SNAPSHOT).
Have this as of yesterday.
BETTER solution is to have the TP definitions versioned to match their path/filename.
Thus:
* poms in build/target-platforms/jbdevstudio-JunoSR1a (regardless of master or Beta2x
branch) should be versioned 6.0.0.JunoSR1a
* poms in build/target-platforms/jbosstools-JunoSR0c (regardless of master or Beta2x
branch) should be versioned 4.0.0.JunoSR0c
--
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
3:39 a.m.
[
https://issues.jboss.org/browse/JBIDE-13058?page=com.atlassian.jira.plugi...
]
Mickael Istria edited comment on JBIDE-13058 at 11/22/12 4:37 AM:
------------------------------------------------------------------
Since my JBIDE-13058 branch (
https://github.com/mickaelistria/jbosstools-build/tree/JBIDE-13058 )was forked from master
after 4.0.x branch was forked, I think it'll way easier to change it as part of the
4.1 stream.
Also, it's just an enhancement, so let's postpone it (just) after GA.
was (Author: mickael_istria):
Since my JBIDE-13058 branch was forked from master after 4.0.x branch was forked, I
think it'll way easier to change it as part of the 4.1 stream.
Also, it's just an enhancement, so let's postpone it (just) after GA.
decouple versioning of parent pom from that of target platforms
because some TPs are used for multiple parent poms
------------------------------------------------------------------------------------------------------------------
Key: JBIDE-13058
URL: https://issues.jboss.org/browse/JBIDE-13058
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng, target-platform
Affects Versions: 4.0.0.Beta2
Reporter: Nick Boldt
Assignee: Mickael Istria
Labels: respin-a
Fix For: 4.1.0.Alpha1
Currently, we have parent pom versioned 4.0.0.Beta2-SNAPSHOT (Beta2x branch) or
4.0.0.CR1-SNAPSHOT (master). This is fine.
However, we also have the same versions set for the various target platforms. This is no
longer fine, because while the TP definition is the same between the stable_branch and
trunk jobs, the VERSION differs and that means we have to publish the job TWICE to get the
correct artifacts into Nexus.
Overkill solution is to have 2 jobs for every TP definition - one for stable branch
(versioned 4.0.0.Beta2-SNAPSHOT) and another for trunk (versioned 4.0.0.CR1-SNAPSHOT).
Have this as of yesterday.
BETTER solution is to have the TP definitions versioned to match their path/filename.
Thus:
* poms in build/target-platforms/jbdevstudio-JunoSR1a (regardless of master or Beta2x
branch) should be versioned 6.0.0.JunoSR1a
* poms in build/target-platforms/jbosstools-JunoSR0c (regardless of master or Beta2x
branch) should be versioned 4.0.0.JunoSR0c
--
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
3:05 a.m.
[
https://issues.jboss.org/browse/JBIDE-13058?page=com.atlassian.jira.plugi...
]
Mickael Istria resolved JBIDE-13058.
------------------------------------
Resolution: Done
decouple versioning of parent pom from that of target platforms
because some TPs are used for multiple parent poms
------------------------------------------------------------------------------------------------------------------
Key: JBIDE-13058
URL: https://issues.jboss.org/browse/JBIDE-13058
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng, target-platform
Affects Versions: 4.0.0.Beta2
Reporter: Nick Boldt
Assignee: Mickael Istria
Labels: respin-a
Fix For: 4.1.0.Alpha1
Currently, we have parent pom versioned 4.0.0.Beta2-SNAPSHOT (Beta2x branch) or
4.0.0.CR1-SNAPSHOT (master). This is fine.
However, we also have the same versions set for the various target platforms. This is no
longer fine, because while the TP definition is the same between the stable_branch and
trunk jobs, the VERSION differs and that means we have to publish the job TWICE to get the
correct artifacts into Nexus.
Overkill solution is to have 2 jobs for every TP definition - one for stable branch
(versioned 4.0.0.Beta2-SNAPSHOT) and another for trunk (versioned 4.0.0.CR1-SNAPSHOT).
Have this as of yesterday.
BETTER solution is to have the TP definitions versioned to match their path/filename.
Thus:
* poms in build/target-platforms/jbdevstudio-JunoSR1a (regardless of master or Beta2x
branch) should be versioned 6.0.0.JunoSR1a
* poms in build/target-platforms/jbosstools-JunoSR0c (regardless of master or Beta2x
branch) should be versioned 4.0.0.JunoSR0c
--
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
4874
days inactive
4889
days old
jbosstools-issues@lists.jboss.org
19 comments
3 participants
participants (3)
-
Mickael Istria (JIRA) -
Nick Boldt (JIRA)
-
Rob Cernich (JIRA)