Menu
▾
▴
openoss-devel — OpenOSS Developer Mailing List
You can subscribe to this list here.
| 2004 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2009 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(53) |
Aug
(86) |
Sep
(55) |
Oct
(19) |
Nov
(12) |
Dec
(9) |
| 2010 |
Jan
(8) |
Feb
(32) |
Mar
(31) |
Apr
(70) |
May
(67) |
Jun
(71) |
Jul
(26) |
Aug
(47) |
Sep
(25) |
Oct
(16) |
Nov
(11) |
Dec
(16) |
| 2011 |
Jan
(30) |
Feb
(31) |
Mar
(71) |
Apr
(64) |
May
(55) |
Jun
(25) |
Jul
(3) |
Aug
(24) |
Sep
(20) |
Oct
(18) |
Nov
(21) |
Dec
(1) |
| 2012 |
Jan
(9) |
Feb
(21) |
Mar
(29) |
Apr
(9) |
May
(9) |
Jun
(54) |
Jul
(37) |
Aug
(24) |
Sep
(43) |
Oct
(34) |
Nov
(25) |
Dec
(27) |
| 2013 |
Jan
(5) |
Feb
(13) |
Mar
(23) |
Apr
(9) |
May
(11) |
Jun
|
Jul
(2) |
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
|
| 2014 |
Jan
(1) |
Feb
|
Mar
(3) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Flauw, M. <Mar...@hp...> - 2012-12-10 06:56:03
|
Hi Sitaraman, Tigerstripe uses the notion of Generators and we already have multiple of those, like doc Generator, SOAP Generator, JvtSpec Generator, SoapImpl Generator, EjbImpl Generator. The generators work on Tigerstripe model. They are not plugins, which is a term reserved for eclipse plugins. There is no problem adding a new generator. Look at the Code Generation section of the Tigerstripe documentation: http://wiki.eclipse.org/Tigerstripe_Tutorials#Code_Generation Best regards Marc -----Original Message----- From: sit...@nm... [mailto:sit...@nm...] Sent: Monday, December 10, 2012 4:19 AM To: ope...@li... Subject: [Openoss-devel] Tigerstripe implementation of JOSIF for Texo Integration Hi, I am exploring a possible integration of Texo into the JOSIF tooling. Would appreciate some pointers on what needs to be done at the JOSIF end. Is JOSIF developed as a plugin into Tigerstripe? Could i add the TExo generation as a separate plugin and get the Texo capabilities integrated with JOSIF or should i change the existing code generation plugin....what would you recommend? Thanks Sitaraman -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ------------------------------------------------------------------------------ LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d _______________________________________________ Openoss-devel mailing list Ope...@li... https://lists.sourceforge.net/lists/listinfo/openoss-devel |
|
From: <sit...@nm...> - 2012-12-10 06:29:09
|
Hi Pierre, Yes and no, Texo based generation from XSD, at least for the default configurations, is quite straightforward...also Texo appears configurable from what the site describes. Therefore what i am proposing is we generate JPA annotations from XSDs as a proof of concept and whet things out. Then if things are found to be good then, we can look at integrating Texo capabilities into existing JOSIF geeration...i believe ultimately we must have them as one unit and not just generting JPA annotations from XSD as a standalone entity...What do you think? We need to fix an interface with which we will PoC this out...how about the inventory interface GU? Let me know and thanks much for your continued guidance and support... Sitaraman > Currently the Persistency stack is driven by the procesing of the > tigerstripe dsl into JPA I think what you are suggesting is the processing > the Tooling generated XSD to JPA. So a new generator maybe a better > choice. > > Pierre > > On 2012-12-09, at 10:37 PM, "sit...@nm..." > <sit...@nm...> wrote: > >> Hi, >> I am exploring a possible integration of Texo into the JOSIF tooling. >> Would appreciate some pointers on what needs to be done at the JOSIF >> end. >> Is JOSIF developed as a plugin into Tigerstripe? Could i add the TExo >> generation as a separate plugin and get the Texo capabilities integrated >> with JOSIF or should i change the existing code generation >> plugin....what >> would you recommend? >> Thanks >> Sitaraman >> >> >> -- >> This message has been scanned for viruses and >> dangerous content by MailScanner, and is >> believed to be clean. >> >> >> ------------------------------------------------------------------------------ >> LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial >> Remotely access PCs and mobile devices and provide instant support >> Improve your efficiency, and focus on delivering more value-add services >> Discover what IT Professionals Know. Rescue delivers >> http://p.sf.net/sfu/logmein_12329d2d >> _______________________________________________ >> Openoss-devel mailing list >> Ope...@li... >> https://lists.sourceforge.net/lists/listinfo/openoss-devel >> > > > -- > This message has been scanned for viruses and > dangerous content by MailScanner, and is > believed to be clean. > > -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. |
|
From: Pierre G. <pga...@tm...> - 2012-12-10 06:18:06
|
Currently the Persistency stack is driven by the procesing of the tigerstripe dsl into JPA I think what you are suggesting is the processing the Tooling generated XSD to JPA. So a new generator maybe a better choice. Pierre On 2012-12-09, at 10:37 PM, "sit...@nm..." <sit...@nm...> wrote: > Hi, > I am exploring a possible integration of Texo into the JOSIF tooling. > Would appreciate some pointers on what needs to be done at the JOSIF end. > Is JOSIF developed as a plugin into Tigerstripe? Could i add the TExo > generation as a separate plugin and get the Texo capabilities integrated > with JOSIF or should i change the existing code generation plugin....what > would you recommend? > Thanks > Sitaraman > > > -- > This message has been scanned for viruses and > dangerous content by MailScanner, and is > believed to be clean. > > > ------------------------------------------------------------------------------ > LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial > Remotely access PCs and mobile devices and provide instant support > Improve your efficiency, and focus on delivering more value-add services > Discover what IT Professionals Know. Rescue delivers > http://p.sf.net/sfu/logmein_12329d2d > _______________________________________________ > Openoss-devel mailing list > Ope...@li... > https://lists.sourceforge.net/lists/listinfo/openoss-devel > |
|
From: <sit...@nm...> - 2012-12-10 03:36:53
|
Hi, I am exploring a possible integration of Texo into the JOSIF tooling. Would appreciate some pointers on what needs to be done at the JOSIF end. Is JOSIF developed as a plugin into Tigerstripe? Could i add the TExo generation as a separate plugin and get the Texo capabilities integrated with JOSIF or should i change the existing code generation plugin....what would you recommend? Thanks Sitaraman -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. |
|
From: Pierre G. <pga...@tm...> - 2012-12-07 15:16:50
|
Hi Marc, The issues against the SOAP GEN and SID Import should be tracked under the JOSIF project (for now). Pierre On 2012-12-07, at 2:35 AM, "Flauw, Marc" <Mar...@hp...<mailto:Mar...@hp...>> wrote: Second, I don’t really like the split in projects, as the issues I am reporting against the xsd generation project are in fact josif issues on either the SOAP Gen or the SID Import. |
|
From: Flauw, M. <Mar...@hp...> - 2012-12-07 07:37:06
|
Hi Pierre, I have played a bit with JIRA, creating a story and some issues. First, please add Yong-Jie He I nthe list of maintainer. I was not able to assign an issue to him. Second, I don't really like the split in projects, as the issues I am reporting against the xsd generation project are in fact josif issues on either the SOAP Gen or the SID Import. So I don't really know where to put them. I was also confused by not having any component. I was looking for a place to indicate that this relates to the SOAP Gen or to the SID Import. This would allow default maintainer per component. I tried once using a keyword, but it is not equivalent. Best regards Marc |
|
From: Flauw, M. <Mar...@hp...> - 2012-12-05 13:58:46
|
Hi Craig, In the JOSIF guidebook page, some of the pointers in the table of contents are greyed and not useable while it seems the content is there. I browsed some pages and the data seemed ok. I have added some stuff in the Setting up the environment. Some java compiler preferences to detect SID duplicate fields/ attributes. Best regards Marc -----Original Message----- From: Craig Gallen (opennms) [mailto:cg...@op...] Sent: Tuesday, December 04, 2012 4:27 AM To: openoss-devel; Craig Gallen (OpenNMS) Subject: [Openoss-devel] New wiki for OpenOSS. Hi, In time for Management world. I've done a lot of work migrating the old media wiki to confluence before it gets switched off. Still a bit of tidying up to do and a few broken links. However most of the content seems to have migrated OK. For now I have basically moved the content much as is but confluence allows us to order the content better so I'll be working with Pierre to restructure the site and integrate with Jira. By the end of this week I hope to be in a position to redirect the main page to this site. have a look at https://openoss.atlassian.net/wiki/display/WD/JOSIF+Main+Page Feedback appreciated - in particular if there is key content which has not travelled correctly. Craig ------------------------------------------------------------------------------ LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d _______________________________________________ Openoss-devel mailing list Ope...@li... https://lists.sourceforge.net/lists/listinfo/openoss-devel |
|
From: Xose R. S. V. <xr...@op...> - 2012-12-04 10:32:30
|
I have evaluated it and seems that the file 'internal_primitives.xsd' doesn't support the ArrayOf URIs. This file is generated in the packages TIP_Common_SoapSpecPackage and TIP_Generator_Internal_SoapSpecPackage and there is no support for ArrayOfURI. When we have added the support to hte URI some months ago we doesn't include this feature. If you want I can try and test and include it in the projects but I don't know if there are someone in charge of these packages. Regards El 23/11/2012 17:20, Flauw, Marc escribió: > > Xose, > > I have found another problem. > > When an attribute is of type primitive.uri and multiplicity is *, what > is generated is something like > > <xsd:element name="reference" type="primitives:ArrayOfAnyURI" > minOccurs="0" maxOccurs="1"> > > However, when opening the xsd under eclipse and going to source view, > eclipse flags the following problem: > > src-resolve: Cannot resolve the name 'primitives:ArrayOfAnyURI' to > a(n) 'type definition' component. > > Thanks and regards > > Marc > > *From:*Xose Ramon Sousa Vazquez [mailto:xr...@op...] > *Sent:* Thursday, November 22, 2012 11:18 AM > *To:* Flauw, Marc > *Cc:* Pierre Gauthier (pga...@tm...); > ope...@li... > *Subject:* Re: SOAP Error while generating SID 12.5 > > I will check it and give some feedback as soon as possible. > > Regards > El 22/11/2012 8:08, Flauw, Marc escribió: > > Xose, > > While generating the SID 12.5 with the V1.1.2 generators, I have > some errors: > > 1) for the packages in the common model, the SOAP generator is > generating dep files, so I have 4 dep files generated: > dep_cbe_base.xsd, dep_cbe_job.xsd, dep_cbe_time_sched.xsd, > dep_resource_res_nrb.xsd. In the spec_package step, the > corresponding common files are added, but the dep ones are still > there. It looks like the SOAP generator does not recognize those > files as being common files. > > 2) when opening sid_cbe_bi.xsd, the xml validator complains that > it cannot find dep_java_sql.xsd. There is no such file and it is > not referenced directly from this file. A number of sid file seems > to reference this file also. > > The projects are available under svn: > http://collab.tmforum.org/svn/repos/tip/Features/SID xsd > Generation/InfoModel/trunk > <http://collab.tmforum.org/svn/repos/tip/Features/SID%20xsd%20Generation/InfoModel/trunk> > > The src files are not under svn, I will send them separately along > with the generated kit. > > Best regards > > Marc > > -- > > *Xose Ramon Sousa Vazquez*| Director OSS Technologies, Director I+D > T/ + 34 986 410 091 (ext) 206 | M/ +34 675 550 029 > www.optaresolutions.com > <http://www.optaresolutions.com> > Optare Solutions <http://optarecoolvendor.com> > -- *Xose Ramon Sousa Vazquez* | Director OSS Technologies, Director I+D T/ + 34 986 410 091 (ext) 206 | M/ +34 675 550 029 www.optaresolutions.com <http://www.optaresolutions.com> Optare Solutions <http://optarecoolvendor.com> |
|
From: Craig G. (opennms) <cg...@op...> - 2012-12-04 03:27:17
|
Hi, In time for Management world. I've done a lot of work migrating the old media wiki to confluence before it gets switched off. Still a bit of tidying up to do and a few broken links. However most of the content seems to have migrated OK. For now I have basically moved the content much as is but confluence allows us to order the content better so I'll be working with Pierre to restructure the site and integrate with Jira. By the end of this week I hope to be in a position to redirect the main page to this site. have a look at https://openoss.atlassian.net/wiki/display/WD/JOSIF+Main+Page Feedback appreciated - in particular if there is key content which has not travelled correctly. Craig |
|
From: Pierre G. <pga...@tm...> - 2012-12-03 22:29:23
|
Hi All, Please make sure that we have a JIRA issue tracking this problem. Pierre On Dec 3, 2012, at 11:55 AM, Xose Ramon Sousa Vazquez <xr...@op...<mailto:xr...@op...>> wrote: Hi Marc. It seems that the problem could be derivated because of when the support for URI was added, the support for the ArrayOfURI was not included. I wil check it. Regards El 03/12/2012 11:14, Flauw, Marc escribió: Hi Xose, After fixing a number of other problems in the SID, there is still a problem of unresolved type with ArrayOfAnyURI. This occurs when an attribute has a type of primitive.uri and a multiplicity of * Any idea? Best regards Marc -----Original Message----- From: Ramachandran Vilayannur [mailto:vpa...@gm...] Sent: Monday, December 03, 2012 10:08 AM To: Flauw, Marc Cc: sit...@nm...<mailto:sit...@nm...> Subject: Re: SID Sandbox branch Hi Marc, I get the following errors...where is the arrayOfAnyURI defined and how to include them in the SID XSDs.. Thanks java.lang.IllegalStateException: file:/D:/Users/Sitaraman/EclipseVersions/EclipseForEMF/workspace/TexoTest1/Model/WSDL/sid_enterprise_risk_sec_vuln.xsd<file:///D:/Users/Sitaraman/EclipseVersions/EclipseForEMF/workspace/TexoTest1/Model/WSDL/sid_enterprise_risk_sec_vuln.xsd> (254:17):XSD: Type reference 'http://www.tmforum.org/xml/tip/internal/primitives#ArrayOfAnyURI' is unresolved file:/D:/Users/Sitaraman/EclipseVersions/EclipseForEMF/workspace/TexoTest1/Model/WSDL/sid_enterprise_risk_sec_threat.xsd<file:///D:/Users/Sitaraman/EclipseVersions/EclipseForEMF/workspace/TexoTest1/Model/WSDL/sid_enterprise_risk_sec_threat.xsd> (279:17):XSD: Type reference 'http://www.tmforum.org/xml/tip/internal/primitives#ArrayOfAnyURI' is unresolved file:/D:/Users/Sitaraman/EclipseVersions/EclipseForEMF/workspace/TexoTest1/Model/WSDL/sid_enterprise_risk_sec_threat.xsd<file:///D:/Users/Sitaraman/EclipseVersions/EclipseForEMF/workspace/TexoTest1/Model/WSDL/sid_enterprise_risk_sec_threat.xsd> (480:17):XSD: Type reference 'http://www.tmforum.org/xml/tip/internal/primitives#ArrayOfAnyURI' is unresolved Sitaraman -- Xose Ramon Sousa Vazquez | Director OSS Technologies, Director I+D T/ + 34 986 410 091 (ext) 206 | M/ +34 675 550 029 www.optaresolutions.com <http://www.optaresolutions.com/> <optareemailsignature.jpg> <http://optarecoolvendor.com/> |
|
From: Xose R. S. V. <xr...@op...> - 2012-12-03 16:57:34
|
Hi Marc. It seems that the problem could be derivated because of when the support for URI was added, the support for the ArrayOfURI was not included. I wil check it. Regards El 03/12/2012 11:14, Flauw, Marc escribió: > Hi Xose, > > After fixing a number of other problems in the SID, there is still a problem of unresolved type with ArrayOfAnyURI. > > This occurs when an attribute has a type of primitive.uri and a multiplicity of * > > Any idea? > > Best regards > > Marc > > -----Original Message----- > From: Ramachandran Vilayannur [mailto:vpa...@gm...] > Sent: Monday, December 03, 2012 10:08 AM > To: Flauw, Marc > Cc: sit...@nm... > Subject: Re: SID Sandbox branch > > Hi Marc, > I get the following errors...where is the arrayOfAnyURI defined and how to include them in the SID XSDs.. Thanks > java.lang.IllegalStateException: > file:/D:/Users/Sitaraman/EclipseVersions/EclipseForEMF/workspace/TexoTest1/Model/WSDL/sid_enterprise_risk_sec_vuln.xsd > (254:17):XSD: Type reference > 'http://www.tmforum.org/xml/tip/internal/primitives#ArrayOfAnyURI' is unresolved file:/D:/Users/Sitaraman/EclipseVersions/EclipseForEMF/workspace/TexoTest1/Model/WSDL/sid_enterprise_risk_sec_threat.xsd > (279:17):XSD: Type reference > 'http://www.tmforum.org/xml/tip/internal/primitives#ArrayOfAnyURI' is unresolved file:/D:/Users/Sitaraman/EclipseVersions/EclipseForEMF/workspace/TexoTest1/Model/WSDL/sid_enterprise_risk_sec_threat.xsd > (480:17):XSD: Type reference > 'http://www.tmforum.org/xml/tip/internal/primitives#ArrayOfAnyURI' is unresolved > > Sitaraman > -- *Xose Ramon Sousa Vazquez* | Director OSS Technologies, Director I+D T/ + 34 986 410 091 (ext) 206 | M/ +34 675 550 029 www.optaresolutions.com <http://www.optaresolutions.com> Optare Solutions <http://optarecoolvendor.com> |
|
From: Xose R. S. V. <xr...@op...> - 2012-12-03 10:18:34
|
Ok.
I will change the workaround and perform a test (it takes a long time)
and the will send the workaround again
Regards
El 03/12/2012 11:11, Flauw, Marc escribió:
>
> Hi Xose,
>
> The SID has no dependencies project or module, so only a single common
> model module.
>
> On your proposed workaround, I would like to remove the dep files not
> the common ones.
>
> I agree common model and dependencies should not share classes and
> they don't for the SID as there is no dependencies module.
>
> Best regards
>
> Marc
>
> *From:*Xose Ramon Sousa Vazquez [mailto:xr...@op...]
> *Sent:* Monday, December 03, 2012 10:07 AM
> *To:* Flauw, Marc
> *Cc:* Pierre Gauthier (pga...@tm...);
> ope...@li...
> *Subject:* Re: SOAP Error while generating SID 12.5
>
> Hi Marc. I have tested some workaround to remove the files. I have
> found one that removes the files, perhaps not the smart one, but I
> think that it would be managed as an exception.
> I think that the common and the dependencies must be complementary
> and not share classes. I think that this could be another discussion.
>
> The workaround includes a detection of the files with the problem and
> removes it if exist.
> You must include these lines with a plugin definition in the pom.xml
> file of SID_SoapSpecPackage project.
>
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-antrun-plugin</artifactId>
> <executions>
> <execution>
> <id>Delete duplicate files</id>
> <phase>generate-sources</phase>
> <configuration>
> <tasks>
> <taskdef resource="net/sf/antcontrib/antlib.xml">
> <classpath refid="maven.dependency.classpath" />
> </taskdef>
>
> <if>
> <available
> file="${project.build.directory}/generated-sources/src/main/wsdl/dep_cbe_base.xsd"
> />
> <then>
> <delete
> file="${project.build.directory}/generated-sources/src/main/wsdl/common_cbe_base.xsd"/>
> </then>
> </if>
> <if>
> <available
> file="${project.build.directory}/generated-sources/src/main/wsdl/dep_cbe_job.xsd"
> />
> <then>
> <delete
> file="${project.build.directory}/generated-sources/src/main/wsdl/common_cbe_job.xsd"/>
> </then>
> </if>
> <if>
> <available
> file="${project.build.directory}/generated-sources/src/main/wsdl/dep_cbe_time_sched.xsd"
> />
> <then>
> <delete
> file="${project.build.directory}/generated-sources/src/main/wsdl/common_cbe_time_sched.xsd"/>
> </then>
> </if>
> <if>
> <available
> file="${project.build.directory}/generated-sources/src/main/wsdl/dep_resource_res_nrb.xsd"
> />
> <then>
> <delete
> file="${project.build.directory}/generated-sources/src/main/wsdl/common_resource_res_nrb.xsd"/>
> </then>
> </if>
> </tasks>
> </configuration>
> <goals>
> <goal>run</goal>
> </goals>
> </execution>
> </executions>
> </plugin>
>
> I have attached the updated file in the email.
>
>
> Best regards
>
>
> El 22/11/2012 8:08, Flauw, Marc escribió:
>
> Xose,
>
> While generating the SID 12.5 with the V1.1.2 generators, I have
> some errors:
>
> 1) for the packages in the common model, the SOAP generator is
> generating dep files, so I have 4 dep files generated:
> dep_cbe_base.xsd, dep_cbe_job.xsd, dep_cbe_time_sched.xsd,
> dep_resource_res_nrb.xsd. In the spec_package step, the
> corresponding common files are added, but the dep ones are still
> there. It looks like the SOAP generator does not recognize those
> files as being common files.
>
> 2) when opening sid_cbe_bi.xsd, the xml validator complains that
> it cannot find dep_java_sql.xsd. There is no such file and it is
> not referenced directly from this file. A number of sid file seems
> to reference this file also.
>
> The projects are available under svn:
> http://collab.tmforum.org/svn/repos/tip/Features/SID xsd
> Generation/InfoModel/trunk
> <http://collab.tmforum.org/svn/repos/tip/Features/SID%20xsd%20Generation/InfoModel/trunk>
>
> The src files are not under svn, I will send them separately along
> with the generated kit.
>
> Best regards
>
> Marc
>
> --
>
> *Xose Ramon Sousa Vazquez*| Director OSS Technologies, Director I+D
> T/ + 34 986 410 091 (ext) 206 | M/ +34 675 550 029
> www.optaresolutions.com
> <http://www.optaresolutions.com>
> Optare Solutions <http://optarecoolvendor.com>
>
--
*Xose Ramon Sousa Vazquez* | Director OSS Technologies, Director I+D
T/ + 34 986 410 091 (ext) 206 | M/ +34 675 550 029
www.optaresolutions.com
<http://www.optaresolutions.com>
Optare Solutions <http://optarecoolvendor.com>
|
|
From: Flauw, M. <Mar...@hp...> - 2012-12-03 10:15:10
|
Hi Xose, After fixing a number of other problems in the SID, there is still a problem of unresolved type with ArrayOfAnyURI. This occurs when an attribute has a type of primitive.uri and a multiplicity of * Any idea? Best regards Marc -----Original Message----- From: Ramachandran Vilayannur [mailto:vpa...@gm...] Sent: Monday, December 03, 2012 10:08 AM To: Flauw, Marc Cc: sit...@nm... Subject: Re: SID Sandbox branch Hi Marc, I get the following errors...where is the arrayOfAnyURI defined and how to include them in the SID XSDs.. Thanks java.lang.IllegalStateException: file:/D:/Users/Sitaraman/EclipseVersions/EclipseForEMF/workspace/TexoTest1/Model/WSDL/sid_enterprise_risk_sec_vuln.xsd (254:17):XSD: Type reference 'http://www.tmforum.org/xml/tip/internal/primitives#ArrayOfAnyURI' is unresolved file:/D:/Users/Sitaraman/EclipseVersions/EclipseForEMF/workspace/TexoTest1/Model/WSDL/sid_enterprise_risk_sec_threat.xsd (279:17):XSD: Type reference 'http://www.tmforum.org/xml/tip/internal/primitives#ArrayOfAnyURI' is unresolved file:/D:/Users/Sitaraman/EclipseVersions/EclipseForEMF/workspace/TexoTest1/Model/WSDL/sid_enterprise_risk_sec_threat.xsd (480:17):XSD: Type reference 'http://www.tmforum.org/xml/tip/internal/primitives#ArrayOfAnyURI' is unresolved Sitaraman |
|
From: Craig G. (opennms) <cg...@op...> - 2012-11-28 16:28:17
|
Hi Pierre, I see you have started creating a number of spaces in confluence. Great. I am in the process of trying to migrate our media wiki content into the wiki under what is called the imported space for now. Once it is migrated, then we can work on formatting for the new wiki. Ive done quite a bit with confluence over the last year and from my experience I think it would be better to put the majority of projects as sub-categories within one 'developers' space rather than create a new space for each project. The intention of the space system is to allow us to have completely isolated spaces with different users and access permissions. In Apache's use of confluence they appear to use one space per project. It is a little difficult to move content between spaces and also to ensure that search works across spaces. By all means have a play but don't get carried away with too many spaces. If we create too many separate spaces everything becomes a bit difficult to control. It is probably better to limit the number of spaces we use (much as in a normal wiki where there is no concept of spaces). Cheers Craig |
|
From: Xose R. S. V. <xr...@op...> - 2012-11-22 10:46:06
|
I will check it and give some feedback as soon as possible. Regards El 22/11/2012 8:08, Flauw, Marc escribió: > > Xose, > > While generating the SID 12.5 with the V1.1.2 generators, I have some > errors: > > 1) for the packages in the common model, the SOAP generator is > generating dep files, so I have 4 dep files generated: > dep_cbe_base.xsd, dep_cbe_job.xsd, dep_cbe_time_sched.xsd, > dep_resource_res_nrb.xsd. In the spec_package step, the corresponding > common files are added, but the dep ones are still there. It looks > like the SOAP generator does not recognize those files as being common > files. > > 2) when opening sid_cbe_bi.xsd, the xml validator complains that it > cannot find dep_java_sql.xsd. There is no such file and it is not > referenced directly from this file. A number of sid file seems to > reference this file also. > > The projects are available under svn: > http://collab.tmforum.org/svn/repos/tip/Features/SID xsd > Generation/InfoModel/trunk > <http://collab.tmforum.org/svn/repos/tip/Features/SID%20xsd%20Generation/InfoModel/trunk> > > The src files are not under svn, I will send them separately along > with the generated kit. > > Best regards > > Marc > -- *Xose Ramon Sousa Vazquez* | Director OSS Technologies, Director I+D T/ + 34 986 410 091 (ext) 206 | M/ +34 675 550 029 www.optaresolutions.com <http://www.optaresolutions.com> Optare Solutions <http://optarecoolvendor.com> |
|
From: Flauw, M. <Mar...@hp...> - 2012-11-22 07:10:16
|
Xose, While generating the SID 12.5 with the V1.1.2 generators, I have some errors: 1) for the packages in the common model, the SOAP generator is generating dep files, so I have 4 dep files generated: dep_cbe_base.xsd, dep_cbe_job.xsd, dep_cbe_time_sched.xsd, dep_resource_res_nrb.xsd. In the spec_package step, the corresponding common files are added, but the dep ones are still there. It looks like the SOAP generator does not recognize those files as being common files. 2) when opening sid_cbe_bi.xsd, the xml validator complains that it cannot find dep_java_sql.xsd. There is no such file and it is not referenced directly from this file. A number of sid file seems to reference this file also. The projects are available under svn: http://collab.tmforum.org/svn/repos/tip/Features/SID xsd Generation/InfoModel/trunk<http://collab.tmforum.org/svn/repos/tip/Features/SID%20xsd%20Generation/InfoModel/trunk> The src files are not under svn, I will send them separately along with the generated kit. Best regards Marc |
|
From: Craig G. (opennms) <cg...@op...> - 2012-11-20 19:50:59
|
Hi, Just to let people know that I have started the porting of the Mediawiki to the sourceforge hosted apps site. The new wiki address is http://openoss.sourceforge.net/mwiki/index.php/Main_Page This has gone fairly smoothly although it has taken several days to sort out the details. The login mechanism is not yet working and there are a few teething problems as yet with rendering images. However I am using a backup of the main wiki site taken a couple of days ago. I suggest you hold off any more changes to the active Wiki until this migration is complete. Thanks Craig |
|
From: Xose R. S. V. <xr...@op...> - 2012-11-15 14:46:52
|
Hi Pierre, I have reproduced the error. I think that the main problem is
the cache mechanism used by Tigerstripe in the dependencies. I have had
similar problems in the development of external xsd support.
The problem is that the libraries included sometimes are not updated in
the tigerstripe environments. To update it you must delete the
dependendencies and recreate again. I am using a quick approach of edit
the tigerstripe.xml file in the Model project and change the order of
the libraries. This implies a refresh in the libreries used.
FROM
<dependencies>
<dependency enabled="true" path="org.tmforum.tip.fmk.common_1.1.jar"/>
<dependency enabled="true" path="TIP_INV_2.0.dep_0.0.jar"/>
</dependencies>
TO
<dependencies>
<dependency enabled="true" path="TIP_INV_2.0.dep_0.0.jar"/>
<dependency enabled="true" path="org.tmforum.tip.fmk.common_1.1.jar"/>
</dependencies>
Also I detect another small elements to change:
.Errors with characters`` ´´ that are not supported in UTF-8 in the
Model project.
.Definition and locations of packages in .inventory
.Generators enabled (Jvt and SopaImpl are deselected)
.Some project elements as .project .visualstate, etc that are
independent so would be removed
Regards
El 13/11/2012 1:43, pierre gauthier escribió:
> Hi Xose,
>
> I'm trying to compile a new version of the Inventory Spec and now getting a new error on
> dependancy project. This happen when I use the fmw library which has a resource.res
> package and the dependancy also containing a resource.res package.
>
> You can reproduce the problem by using the inventory branches project in svn http://collab.tmforum.org/svn/repos/tip/Features/InventoryManagement/IA/InterfaceModel/branches/v12
>
>
> The error is java.io.FileNotFoundException: C:\inventoryworkspace\TIP_INV_SoapSpecPackage\tip_inv_dependencies_resource_res.xsd (The system cannot find the file specified)
>
> Thanks Pierre
>
>
--
*Xose Ramon Sousa Vazquez* | Director OSS Technologies, Director I+D
T/ + 34 986 410 091 (ext) 206 | M/ +34 675 550 029
www.optaresolutions.com
<http://www.optaresolutions.com>
Optare Solutions <http://optarecoolvendor.com><http://optarecoolvendor.com>
|
|
From: Pierre G. <pga...@tm...> - 2012-11-13 20:33:08
|
Ho Xose, I got similar problems with the Customer Management API not generation the Time dependancy xsd properly. You can try it from http://collab.tmforum.org/svn/repos/tip/Features/Customer%20ABE/IA/Model/trunk Regards Pierre |
|
From: Xose R. S. V. <xr...@op...> - 2012-11-13 10:32:38
|
ok Pierre. I will check it. Regards El 13/11/2012 1:43, pierre gauthier escribió: > Hi Xose, > > I'm trying to compile a new version of the Inventory Spec and now getting a new error on > dependancy project. This happen when I use the fmw library which has a resource.res > package and the dependancy also containing a resource.res package. > > You can reproduce the problem by using the inventory branches project in svn http://collab.tmforum.org/svn/repos/tip/Features/InventoryManagement/IA/InterfaceModel/branches/v12 > > > The error is java.io.FileNotFoundException: C:\inventoryworkspace\TIP_INV_SoapSpecPackage\tip_inv_dependencies_resource_res.xsd (The system cannot find the file specified) > > Thanks Pierre > > -- *Xose Ramon Sousa Vazquez* | Director OSS Technologies, Director I+D T/ + 34 986 410 091 (ext) 206 | M/ +34 675 550 029 www.optaresolutions.com <http://www.optaresolutions.com> Optare Solutions <http://optarecoolvendor.com><http://optarecoolvendor.com> |
|
From: pierre g. <pie...@os...> - 2012-11-13 01:11:38
|
Hi Xose, I'm trying to compile a new version of the Inventory Spec and now getting a new error on dependancy project. This happen when I use the fmw library which has a resource.res package and the dependancy also containing a resource.res package. You can reproduce the problem by using the inventory branches project in svn http://collab.tmforum.org/svn/repos/tip/Features/InventoryManagement/IA/InterfaceModel/branches/v12 The error is java.io.FileNotFoundException: C:\inventoryworkspace\TIP_INV_SoapSpecPackage\tip_inv_dependencies_resource_res.xsd (The system cannot find the file specified) Thanks Pierre |
|
From: Craig G. (opennms) <cg...@op...> - 2012-11-07 16:53:49
|
If I understand your question. you need to use the command mvn eclipse:eclipse on the base project to create the eclipse project files so that a project can be visible in the eclipse workspace then you should be able to import them as existing projects into the workspace Craig On 07/11/2012 16:19, Josh Salomon wrote: > > It seems to work, and the build completed successfully! Many thanks, Craig > > Now for a dumb question L > > When I open eclipse I cannot find an existing project for the sample > workspace (TIP_Test ....) > > Where is the workspace/project with the existing work so I can open it? > > Regards, > > Josh > > *From:*Josh Salomon > *Sent:* Wednesday, November 07, 2012 2:04 PM > *To:* Craig Gallen (opennms) > *Cc:* openoss-devel; Flauw, Marc > *Subject:* Re: [Openoss-devel] [SPAM]:. Re: FW: JOSIF build > > Thanks, Craig, > > I started with ver 1.1.1 and now I am going to install 1.1.2 instead > -- I hope this will help me let you know when I finish. > > Regards, > > Josh > > *From:*Craig Gallen [mailto:gal...@go...] *On Behalf Of > *Craig Gallen (opennms) > *Sent:* Wednesday, November 07, 2012 2:00 PM > *To:* Josh Salomon > *Cc:* Flauw, Marc; openoss-devel > *Subject:* [SPAM]:. Re: [Openoss-devel] FW: JOSIF build > > Hi, > > You seem to be struggling a bit. Ping me on skype if you need help > skype craig.gallen. I'm afraid I am only working on this > intermittently but I will help if I can. > > I'm not sure what configuration you are running but it looks like it > is a bit of a mix and batch between versions. I suggest you try the > following which I made sure works today. > > Firstly you should be using JOSIF Release 1.1.2 as you workbench > starting point. You can get this from > http://sourceforge.net/projects/openoss/files/ This should have the > correct plugins and profile already installed. However all of the > versions of plugins are on this site. > > Please note that JOSIF Release 1.1.1 plugins will not work in the > Release 1.1.2 workbench. Changes have happened in the tigerstripe > API which make the workbench not backwards compatible to old plugins. > If in doubt un-install the plug-ins and install the correct one using > the tigerstripe>Plugins dialogue. Better still check out the Release > 1.1.2 plug-ins from subversion and deploy them directly > > >From the log, you appear to be trying to build RAM release 1.0.1. You > should be building RAM 1.0.2 with JOSIF Release 1.1.2. Check out the > RAM 1.0.2 version from the following tag. > https://collab.tmforum.org/svn/repos/tip/Features/ResourceAlarmManagement/IA/Interface/tags/RELEASE_1_0_2/TIP_RAM_BaseProject > > The RI / CTK are at > https://collab.tmforum.org/svn/repos/tip/Features/ResourceAlarmManagement/IA/RAM_RI_CTK_Project/tags/RELEASE_1_0_2/TIP_RAM_CompatibilityTestKit > > You shouldn't need to change any of the pom.xml files. Just make sure > the tigerstripe.properties file matches your installation in each > Dependencies and Model folder > > Hope this helps > > Craig > > On 06/11/2012 09:07, Josh Salomon wrote: > > This is my fault because of the process I used -- I ran mvn clean > then mvn install and when it failed mvn install again to generate > the log file. > > Apologies for that. > > Attached now is the log for "mvn clean install" -- the bottom line > is the same error but it includes the entire info. > > Many thanks again ! > > Regards, > > Josh > > *From:*Craig Gallen [mailto:gal...@go...] *On > Behalf Of *Craig Gallen (opennms) > *Sent:* Monday, November 05, 2012 9:03 PM > *To:* Josh Salomon > *Cc:* Flauw, Marc; openoss-devel > *Subject:* Re: [Openoss-devel] FW: JOSIF build > > Hi, > from the following lines; > [echo] MODEL_POM: Will not run tigerstripe because > C:\JOSIF\ws-ts-sample\TIP_RAM_Dependencies\target\CODE_GENERATED_FLAG.txt > exists. (Use 'mvn clean install' To run Tigerstripe) > > Looks like you didn't use mvn clean install but just mvn install > > Try mvn clean install to regenerate all the artifacts with the new > plugins > > Craig > > > > On 05/11/2012 16:55, Josh Salomon wrote: > > It seems that I succeeded in progressing a little (I checked > out from the RELEASE_1_0_1 repository on top of my existing > project) but now found a new error. I am posting details to > the community. > > Thanks a lot! > > Regards, > > Josh > > *From:*Flauw, Marc [mailto:Mar...@hp...] > *Sent:* Monday, November 05, 2012 3:33 PM > *To:* Josh Salomon; Craig Gallen (opennms) > *Subject:* [SPAM]:. RE: [Openoss-devel] FW: JOSIF build > > Josh, > > Craig suggested the answer in his initial response: grab the > version of RAM that is aligned with your version of JOSIF. The > pointers are at the bottom of the mail thread. > > Best regards > > Marc > > *From:*Josh Salomon [mailto:JO...@Am...] > *Sent:* Monday, November 05, 2012 2:28 PM > *To:* Craig Gallen (opennms); Flauw, Marc > *Subject:* RE: [Openoss-devel] FW: JOSIF build > > Hi Craig, > > I did not get a reply yet L > > What should I do in order to make JOSIF work? > > I installed the tool using the official installer (V1.1.0), I > followed al the instructions by the letter then the installer > tried to download versions 1.1.0 of the generators which > cannot be found on the network repository > > [INFO] Configured Artifact: > org.tmforum.tip:TIP_Doc_Generator_Package:?:jar > > Downloading: > http://www.ibiblio.org/maven2/org/tmforum/tip/TIP_Doc_Generator_Pac > > kage/1.1.0-SNAPSHOT/TIP_Doc_Generator_Package-1.1.0-SNAPSHOT.jar > > [INFO] Unable to find resource > 'org.tmforum.tip:TIP_Doc_Generator_Package:jar:1. > > 1.0-SNAPSHOT' in repository ibiblio-repo > (http://www.ibiblio.org/maven2) > > Downloading: > https://repository.apache.org/content/repositories/releases//org/tm > <https://repository.apache.org/content/repositories/releases/org/tm> > > forum/tip/TIP_Doc_Generator_Package/1.1.0-SNAPSHOT/TIP_Doc_Generator_Package-1.1 > > .0-SNAPSHOT.jar > > [INFO] Unable to find resource > 'org.tmforum.tip:TIP_Doc_Generator_Package:jar:1. > > 1.0-SNAPSHOT' in repository apache-repo > (https://repository.apache.org/content/r > > epositories/releases/) > > Downloading: > http://openoss.myzen.co.uk/TIP/m2repo-snapshots/org/tmforum/tip/TIP > > _Doc_Generator_Package/1.1.0-SNAPSHOT/TIP_Doc_Generator_Package-1.1.0-SNAPSHOT.j > > ar > > [INFO] Unable to find resource > 'org.tmforum.tip:TIP_Doc_Generator_Package:jar:1. > > 1.0-SNAPSHOT' in repository openoss-tip.snapshots > (http://openoss.myzen.co.uk/TI > > P/m2repo-snapshots) > > Downloading: > http://openoss.myzen.co.uk/TIP/m2repo/org/tmforum/tip/TIP_Doc_Gener > > ator_Package/1.1.0-SNAPSHOT/TIP_Doc_Generator_Package-1.1.0-SNAPSHOT.jar > > [INFO] Unable to find resource > 'org.tmforum.tip:TIP_Doc_Generator_Package:jar:1. > > 1.0-SNAPSHOT' in repository openoss-tip.releases > (http://openoss.myzen.co.uk/TIP > > /m2repo) > > After talking with Marc I changed my POM files to download > version 1.1.1 (snapshot) of the generators, now the download > is OK but still my build fails. According to your email I may > use the wrong SVN repository, however I never set any > repository manually, everything was part of the automatic > installation. Moreover, when I open eclipse, my SVN repository > view is empty and I see no SVN repository. > > Please help me by explaining how I can set the SVN to point at > the right repository. I really want to start working with > JOSIF but it seems like a multi-step challenge every time I > try to install it L > > Regards, > > Josh > > *From:*Craig Gallen [mailto:gal...@go...] > <mailto:[mailto:gal...@go...]> *On Behalf Of > *Craig Gallen (opennms) > *Sent:* Wednesday, October 31, 2012 3:05 PM > *To:* Flauw, Marc > *Cc:* ope...@li... > <mailto:ope...@li...>; Josh Salomon > *Subject:* Re: [Openoss-devel] FW: JOSIF build > > Hi > > It looks like he is building from trunk which wont work with 1.1.1 > > Should he not be using the RELEASE_1_0_2 of ram with 1.2.2 from > https://collab.tmforum.org/svn/repos/tip/Features/ResourceAlarmManagement/IA/Interface/tags/RELEASE_1_0_2/ > > and Release RELEASE_1_0_1 with 1.1.1 from > https://collab.tmforum.org/svn/repos/tip/Features/ResourceAlarmManagement/IA/Interface/tags/RELEASE_1_0_1/ > > Craig > > On 31/10/2012 11:54, Flauw, Marc wrote: > > Dear all, > > Josh has a build error while building RAM with JOSIF 1.1.1: > > [INFO] An Ant BuildException has occured: > C:\JOSIF\ws-ts-sample\TIP_RAM_Spec_Release_Package\src\main\resources\Interface_Implementation_Specifications\WSDL > not found. > > Any idea? > > Best regards > > Marc > > *From:*Josh Salomon [mailto:JO...@Am...] > *Sent:* Wednesday, October 31, 2012 11:16 AM > *To:* Flauw, Marc > *Subject:* JOSIF build > > Hi Marc, > > After I was traveling last week to a customer I am back in > the JOSIF build subject... > > See attached the logs of clean and immediately later > build, it seems there are some issues with the tigerstripe > generators. > > Regards, > > /Josh Salomon > /Amdocs Israel. > Tel: +972-9-7764422 > Fax: +972-9-7761783 > Email: mailto:jo...@am... > > Follow:<http://twitter.com/josh4104> > > This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement, > > you may review athttp://www.amdocs.com/email_disclaimer.asp > > ------------------------------------------------------------------------------ > > Everyone hates slow websites. So do we. > > Make your web apps faster with AppDynamics > > Download AppDynamics Lite for free today: > > http://p.sf.net/sfu/appdyn_sfd2d_oct > > _______________________________________________ > > Openoss-devel mailing list > > Ope...@li... <mailto:Ope...@li...> > > https://lists.sourceforge.net/lists/listinfo/openoss-devel > |
|
From: Craig G. (opennms) <cg...@op...> - 2012-11-07 12:45:03
|
Hi, I haven't seen this before. It looks like you have something running on your machine which is trying to use the same ports as the OpenEJB / Jetty or the JVM. This post might be helpful to help you find which process on your machine is duplicating ports. http://stackoverflow.com/questions/3714957/address-already-in-use-jvm-bind Craig On 06/11/2012 10:07, Vai...@re... wrote: > Dear Craig, > I have build the CTK as well as RI project of PM. > RI is working fine with command *mvn jetty:run-war* > but CTK throws following build error : > *_Embedded error: Address already in use: JVM_Bind_* > ** > i have attached the log file. > Please do the needful. > Thanks and Regards, > *Vaibhav,* > *Reliance Tech Services > *Enjoy the widest reach of 3G services across India only on Reliance > www.rcom.co.in > > > > The information contained in this electronic message (email) and any > attachments to this email are intended for the exclusive use of the > addressee(s) and access to this email by any one else is unauthorised. > The email may contain proprietary, confidential or privileged > information or information relating to Reliance Group. If you are not > the intended recipient, please notify the sender by telephone, fax, or > return email and delete this communication and any attachments > thereto, immediately from your computer. Any dissemination, > distribution, or copying of this communication and the attachments > thereto (in whole or part), in any manner, is strictly prohibited and > actionable at law. The recipient acknowledges that emails are > susceptible to alteration and their integrity can not be guaranteed > and that Company does not guarantee that any e-mail is virus-free and > accept no liability for any damage caused by any virus transmitted by > this email. > = |
|
From: Craig G. (opennms) <cg...@op...> - 2012-11-07 12:00:19
|
Hi, You seem to be struggling a bit. Ping me on skype if you need help skype craig.gallen. I'm afraid I am only working on this intermittently but I will help if I can. I'm not sure what configuration you are running but it looks like it is a bit of a mix and batch between versions. I suggest you try the following which I made sure works today. Firstly you should be using JOSIF Release 1.1.2 as you workbench starting point. You can get this from http://sourceforge.net/projects/openoss/files/ This should have the correct plugins and profile already installed. However all of the versions of plugins are on this site. Please note that JOSIF Release 1.1.1 plugins will not work in the Release 1.1.2 workbench. Changes have happened in the tigerstripe API which make the workbench not backwards compatible to old plugins. If in doubt un-install the plug-ins and install the correct one using the tigerstripe>Plugins dialogue. Better still check out the Release 1.1.2 plug-ins from subversion and deploy them directly From the log, you appear to be trying to build RAM release 1.0.1. You should be building RAM 1.0.2 with JOSIF Release 1.1.2. Check out the RAM 1.0.2 version from the following tag. https://collab.tmforum.org/svn/repos/tip/Features/ResourceAlarmManagement/IA/Interface/tags/RELEASE_1_0_2/TIP_RAM_BaseProject The RI / CTK are at https://collab.tmforum.org/svn/repos/tip/Features/ResourceAlarmManagement/IA/RAM_RI_CTK_Project/tags/RELEASE_1_0_2/TIP_RAM_CompatibilityTestKit You shouldn't need to change any of the pom.xml files. Just make sure the tigerstripe.properties file matches your installation in each Dependencies and Model folder Hope this helps Craig On 06/11/2012 09:07, Josh Salomon wrote: > > This is my fault because of the process I used -- I ran mvn clean then > mvn install and when it failed mvn install again to generate the log file. > > Apologies for that. > > Attached now is the log for "mvn clean install" -- the bottom line is > the same error but it includes the entire info. > > Many thanks again ! > > Regards, > > Josh > > *From:*Craig Gallen [mailto:gal...@go...] *On Behalf Of > *Craig Gallen (opennms) > *Sent:* Monday, November 05, 2012 9:03 PM > *To:* Josh Salomon > *Cc:* Flauw, Marc; openoss-devel > *Subject:* Re: [Openoss-devel] FW: JOSIF build > > Hi, > from the following lines; > [echo] MODEL_POM: Will not run tigerstripe because > C:\JOSIF\ws-ts-sample\TIP_RAM_Dependencies\target\CODE_GENERATED_FLAG.txt > exists. (Use 'mvn clean install' To run Tigerstripe) > > Looks like you didn't use mvn clean install but just mvn install > > Try mvn clean install to regenerate all the artifacts with the new plugins > > Craig > > > > On 05/11/2012 16:55, Josh Salomon wrote: > > It seems that I succeeded in progressing a little (I checked out > from the RELEASE_1_0_1 repository on top of my existing project) > but now found a new error. I am posting details to the community. > > Thanks a lot! > > Regards, > > Josh > > *From:*Flauw, Marc [mailto:Mar...@hp...] > *Sent:* Monday, November 05, 2012 3:33 PM > *To:* Josh Salomon; Craig Gallen (opennms) > *Subject:* [SPAM]:. RE: [Openoss-devel] FW: JOSIF build > > Josh, > > Craig suggested the answer in his initial response: grab the > version of RAM that is aligned with your version of JOSIF. The > pointers are at the bottom of the mail thread. > > Best regards > > Marc > > *From:*Josh Salomon [mailto:JO...@Am...] > *Sent:* Monday, November 05, 2012 2:28 PM > *To:* Craig Gallen (opennms); Flauw, Marc > *Subject:* RE: [Openoss-devel] FW: JOSIF build > > Hi Craig, > > I did not get a reply yet L > > What should I do in order to make JOSIF work? > > I installed the tool using the official installer (V1.1.0), I > followed al the instructions by the letter then the installer > tried to download versions 1.1.0 of the generators which cannot be > found on the network repository > > [INFO] Configured Artifact: > org.tmforum.tip:TIP_Doc_Generator_Package:?:jar > > Downloading: > http://www.ibiblio.org/maven2/org/tmforum/tip/TIP_Doc_Generator_Pac > > kage/1.1.0-SNAPSHOT/TIP_Doc_Generator_Package-1.1.0-SNAPSHOT.jar > > [INFO] Unable to find resource > 'org.tmforum.tip:TIP_Doc_Generator_Package:jar:1. > > 1.0-SNAPSHOT' in repository ibiblio-repo > (http://www.ibiblio.org/maven2) > > Downloading: > https://repository.apache.org/content/repositories/releases//org/tm <https://repository.apache.org/content/repositories/releases/org/tm> > > forum/tip/TIP_Doc_Generator_Package/1.1.0-SNAPSHOT/TIP_Doc_Generator_Package-1.1 > > .0-SNAPSHOT.jar > > [INFO] Unable to find resource > 'org.tmforum.tip:TIP_Doc_Generator_Package:jar:1. > > 1.0-SNAPSHOT' in repository apache-repo > (https://repository.apache.org/content/r > > epositories/releases/) > > Downloading: > http://openoss.myzen.co.uk/TIP/m2repo-snapshots/org/tmforum/tip/TIP > > _Doc_Generator_Package/1.1.0-SNAPSHOT/TIP_Doc_Generator_Package-1.1.0-SNAPSHOT.j > > ar > > [INFO] Unable to find resource > 'org.tmforum.tip:TIP_Doc_Generator_Package:jar:1. > > 1.0-SNAPSHOT' in repository openoss-tip.snapshots > (http://openoss.myzen.co.uk/TI > > P/m2repo-snapshots) > > Downloading: > http://openoss.myzen.co.uk/TIP/m2repo/org/tmforum/tip/TIP_Doc_Gener > > ator_Package/1.1.0-SNAPSHOT/TIP_Doc_Generator_Package-1.1.0-SNAPSHOT.jar > > [INFO] Unable to find resource > 'org.tmforum.tip:TIP_Doc_Generator_Package:jar:1. > > 1.0-SNAPSHOT' in repository openoss-tip.releases > (http://openoss.myzen.co.uk/TIP > > /m2repo) > > After talking with Marc I changed my POM files to download version > 1.1.1 (snapshot) of the generators, now the download is OK but > still my build fails. According to your email I may use the wrong > SVN repository, however I never set any repository manually, > everything was part of the automatic installation. Moreover, when > I open eclipse, my SVN repository view is empty and I see no SVN > repository. > > Please help me by explaining how I can set the SVN to point at the > right repository. I really want to start working with JOSIF but it > seems like a multi-step challenge every time I try to install it L > > Regards, > > Josh > > *From:*Craig Gallen [mailto:gal...@go...] > <mailto:[mailto:gal...@go...]> *On Behalf Of *Craig > Gallen (opennms) > *Sent:* Wednesday, October 31, 2012 3:05 PM > *To:* Flauw, Marc > *Cc:* ope...@li... > <mailto:ope...@li...>; Josh Salomon > *Subject:* Re: [Openoss-devel] FW: JOSIF build > > Hi > > It looks like he is building from trunk which wont work with 1.1.1 > > Should he not be using the RELEASE_1_0_2 of ram with 1.2.2 from > https://collab.tmforum.org/svn/repos/tip/Features/ResourceAlarmManagement/IA/Interface/tags/RELEASE_1_0_2/ > > and Release RELEASE_1_0_1 with 1.1.1 from > https://collab.tmforum.org/svn/repos/tip/Features/ResourceAlarmManagement/IA/Interface/tags/RELEASE_1_0_1/ > > Craig > > On 31/10/2012 11:54, Flauw, Marc wrote: > > Dear all, > > Josh has a build error while building RAM with JOSIF 1.1.1: > > [INFO] An Ant BuildException has occured: > C:\JOSIF\ws-ts-sample\TIP_RAM_Spec_Release_Package\src\main\resources\Interface_Implementation_Specifications\WSDL > not found. > > Any idea? > > Best regards > > Marc > > *From:*Josh Salomon [mailto:JO...@Am...] > *Sent:* Wednesday, October 31, 2012 11:16 AM > *To:* Flauw, Marc > *Subject:* JOSIF build > > Hi Marc, > > After I was traveling last week to a customer I am back in the > JOSIF build subject... > > See attached the logs of clean and immediately later build, it > seems there are some issues with the tigerstripe generators. > > Regards, > > /Josh Salomon > /Amdocs Israel. > Tel: +972-9-7764422 > Fax: +972-9-7761783 > Email: mailto:jo...@am... > > Follow:<http://twitter.com/josh4104> > > This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement, > > you may review athttp://www.amdocs.com/email_disclaimer.asp > > ------------------------------------------------------------------------------ > > Everyone hates slow websites. So do we. > > Make your web apps faster with AppDynamics > > Download AppDynamics Lite for free today: > > http://p.sf.net/sfu/appdyn_sfd2d_oct > > _______________________________________________ > > Openoss-devel mailing list > > Ope...@li... <mailto:Ope...@li...> > > https://lists.sourceforge.net/lists/listinfo/openoss-devel > |
|
From: Craig G. (opennms) <cg...@op...> - 2012-11-07 11:07:46
|
Hi, The archive generators and workbench installers etc should all be available at http://sourceforge.net/projects/openoss/files/JOSIF/ Craig On 31/10/2012 13:34, Josh Salomon wrote: > > Many thanks Craig, > > I used the JOSIF install tool and then changed the POM files to get > generator version 1.1.1 instead of 1.1.0 since 1.1.0 are not available > for downloads any more. > > What should I do now, and how do I get the files from the repository > (If I remember correctly I just used the installer and mvn and did not > connect directly to SVN) > > Regards, > > Josh > > *From:*Craig Gallen [mailto:gal...@go...] *On Behalf Of > *Craig Gallen (opennms) > *Sent:* Wednesday, October 31, 2012 3:05 PM > *To:* Flauw, Marc > *Cc:* ope...@li...; Josh Salomon > *Subject:* Re: [Openoss-devel] FW: JOSIF build > > Hi > > It looks like he is building from trunk which wont work with 1.1.1 > > Should he not be using the RELEASE_1_0_2 of ram with 1.2.2 from > https://collab.tmforum.org/svn/repos/tip/Features/ResourceAlarmManagement/IA/Interface/tags/RELEASE_1_0_2/ > > and Release RELEASE_1_0_1 with 1.1.1 from > https://collab.tmforum.org/svn/repos/tip/Features/ResourceAlarmManagement/IA/Interface/tags/RELEASE_1_0_1/ > > Craig > > On 31/10/2012 11:54, Flauw, Marc wrote: > > Dear all, > > Josh has a build error while building RAM with JOSIF 1.1.1: > > [INFO] An Ant BuildException has occured: > C:\JOSIF\ws-ts-sample\TIP_RAM_Spec_Release_Package\src\main\resources\Interface_Implementation_Specifications\WSDL > not found. > > Any idea? > > Best regards > > Marc > > *From:*Josh Salomon [mailto:JO...@Am...] > *Sent:* Wednesday, October 31, 2012 11:16 AM > *To:* Flauw, Marc > *Subject:* JOSIF build > > Hi Marc, > > After I was traveling last week to a customer I am back in the > JOSIF build subject... > > See attached the logs of clean and immediately later build, it > seems there are some issues with the tigerstripe generators. > > Regards, > > /Josh Salomon > /Amdocs Israel. > Tel: +972-9-7764422 > Fax: +972-9-7761783 > Email: mailto:jo...@am... > > Follow:<http://twitter.com/josh4104> > > This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement, > > you may review athttp://www.amdocs.com/email_disclaimer.asp > > > > > ------------------------------------------------------------------------------ > > Everyone hates slow websites. So do we. > > Make your web apps faster with AppDynamics > > Download AppDynamics Lite for free today: > > http://p.sf.net/sfu/appdyn_sfd2d_oct > > > > > _______________________________________________ > > Openoss-devel mailing list > > Ope...@li... <mailto:Ope...@li...> > > https://lists.sourceforge.net/lists/listinfo/openoss-devel > |
197 messages has been excluded from this view by a project administrator.
